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

Unable to load schema #98

Closed
seahindeniz opened this issue Sep 10, 2020 · 2 comments · Fixed by #112
Closed

Unable to load schema #98

seahindeniz opened this issue Sep 10, 2020 · 2 comments · Fixed by #112
Labels
bug Something isn't working

Comments

@seahindeniz
Copy link

Describe the bug
I just installed the Deno and Denon and started a new project without executing/running anything. I have set up my env. and installed the Deno VSCode extension.
After installing Deno, Denon and creating the denon.json file, the $schema entry shows the following error
Unable to load schema from 'https://deno.land/x/denon/schema.json': Request vscode/content failed unexpectedly without providing any details.(768)

To Reproduce
Steps to reproduce the behavior:
1. Fresh installation
2. Create a new project and JSON file
3. Paste configuration copied from here
4. See error

Screenshots
image
image

Setup

  • OS: Ubuntu 20 on WSL2
  • Deno version: 1.3.3
  • Denon version: 2.3.3

Additional context
If I add the raw schema URL to the denon.json, it works

image

@seahindeniz seahindeniz added the bug Something isn't working label Sep 10, 2020
@notfilippo
Copy link
Collaborator

Mhn. Probably I should start defaulting to the versioned import: https://deno.land/x/denon@2.4.0/schema.json.

@eliassjogreen
Copy link
Member

Are you using a proxy? It seems like that could interfere with schema importing in vscode. According to stackoverflow you should be able to solve this with editing the user settings file to have "http.proxySupport": "off".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants