You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
The text was updated successfully, but these errors were encountered:
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".
hong4rc
added a commit
to hong4rc/denon
that referenced
this issue
Dec 7, 2020
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 errorUnable 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
Setup
Additional context
If I add the raw schema URL to the denon.json, it works
The text was updated successfully, but these errors were encountered: