Open vnalla opened 6 years ago
Related to #431 - "Recognizers often ascribe wrong file type, showing spurious error messages"
Hi @vnalla. We're aware of this issue and plan to fix it in a future sprint. As a workaround, could you please try the following:
It should be re-evaluated by the OpenAPI 2.0 and 3.0 recognizers, which won't find matching content. Thereafter the file should be treated as a plain YAML file, and you should not see those error messages.
Thanks a lot for fixing #439. However the editor shows following error messages if the yaml file does not have OAS spec required properties as shown in the screen shots below. It will be better if the editor can differentiate OAS and non-OAS spec files.
thanks,