Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: Missing required properties error for non-OAS yaml files #444

Open
vnalla opened this issue May 10, 2018 · 2 comments
Open

Question: Missing required properties error for non-OAS yaml files #444

vnalla opened this issue May 10, 2018 · 2 comments

Comments

@vnalla
Copy link

vnalla commented May 10, 2018

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.

object has missing required properties "info", "openapi", "paths"
object has properties "Address" which are not allowed"

image

image

thanks,

@tedepstein
Copy link
Collaborator

Related to #431 - "Recognizers often ascribe wrong file type, showing spurious error messages"

@tedepstein
Copy link
Collaborator

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:

  1. Close the file in the editor.
  2. Open the problems view and, delete the errors on that file.
  3. Re-open the file.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants