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

Bug: Problems loading reference 'openapi-schemas:openapi-2.0.json' #46

Closed
hilleer opened this issue Mar 17, 2020 · 5 comments
Closed

Bug: Problems loading reference 'openapi-schemas:openapi-2.0.json' #46

hilleer opened this issue Mar 17, 2020 · 5 comments

Comments

@hilleer
Copy link

hilleer commented Mar 17, 2020

When installing the extension and opening an OAS file, I get this error:

Problems loading reference 'openapi-schemas:openapi-2.0.json': Unable to load schema from 'openapi-schemas:openapi-2.0.json': Request vscode/content failed with message: cannot open openapi-schemas:openapi-2.0.json. Detail: resource is not available.(768)

Screenshot 2020-03-17 at 14 27 34

@ak1394
Copy link
Collaborator

ak1394 commented Mar 18, 2020

Thanks for reporting the issue! Does it happen with a particular file or all OpenAPI files you tried? In particular does it happen to .json or .yaml files? What's your platform and version of VS Code editor?

@hilleer
Copy link
Author

hilleer commented Mar 19, 2020

Hi @ak1394 ,

Thanks for your response and sorry for not including any of that info at first.

  • It is a .json file, I haven't tried to reproduce with YAML. Can do?
  • Vscode version 1.43.0.
  • Latest version of the extension 2.1.1.

Also, it is in fact a OAS version 3.0.0 file - don't know if that helps.

@hilleer
Copy link
Author

hilleer commented Mar 19, 2020

I tried to reproduce in a new file. I did not see the error until I deleted my original OAS file, then it appeared in the new file. When I restored the deleted file, I did not see the error in that file anymore but only in the "new" file...

@ak1394
Copy link
Collaborator

ak1394 commented Mar 20, 2020

I believe I've fixed the issue, although I could not reproduce it myself. Fix will be available in the next version, please re-open it it still happens to you.

@ak1394 ak1394 closed this as completed Mar 20, 2020
@hilleer
Copy link
Author

hilleer commented Mar 20, 2020

Great. Thanks a lot for looking into it @ak1394 .

ak1394 added a commit that referenced this issue Mar 20, 2020
ak1394 added a commit that referenced this issue Jan 24, 2022
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