Parsing other yaml files leads to problem report without a source about redocly-vs-code

[RomanHotsiy]

Thanks for the report @eseglem 🙌

@tatomyr @roman-sainchuk just making sure you see this ☝️

[RomanHotsiy]

@roman-sainchuk how about if we try to detect openapi from plaintext somehow and show errors only in such case?

[tatomyr]

Hi @eseglem,

What exactly do you mean by custom tags?
Also, could you check if those yaml files are somehow referenced from an actual openapi definition file?

[eseglem]

@tatomyr Custom tags being any local tags that aren't specifically part of the yaml spec. They are left up to the application to handle. Pretty much anything with an ! at the beginning. In the above example this is !GetAtt but the specific tag doesn't matter they all cause the same issue.

In my case they are completely independent and unrelated to openapi. You don't even need to have an openapi definition file to see the problem show up.

Isolated steps to reproduce:

• Open an empty folder in VSCode
• Save the above as example.yaml
• Allow extension to create a redocly.yaml for you.
• You now have 1 problem in example.yaml

[roman-sainchuk]

@eseglem Thanks for reporting! The issue is that extension cannot parse this yaml file so we cannot even determine if the file is the openapi spec or not.
We have to think about how to deal with such cases because we're not sure that showing no errors is acceptable.

[roman-sainchuk]

@RomanHotsiy great idea! We'll try to implement it, thanks!

[eseglem]

I don't think its a horrible thing to report an error, my main issue was that the error does not say it's coming from the Redocly extension. If you catch it and report the error with a source that would be enough to address that concern.

Though I would prefer to see a way to configure which files it tries to parse. Then I could tell it not to do those files. I may have many yaml files across many folders in a repo, but any openapi yaml are in one folder. There is no reason the extension needs to look at the other ones.