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
I'm using VS Code to write command-line tools that use KV, which is currently an unstable API.
For these files, the only way I know to get VS Code to type-check unstable API's is to add this to the top of each file:
/// <reference lib="deno.unstable"/>
Supposedly, setting vscode.unstable to true in .vscode/settings.json should do it, but I've never been able to get it to work.
Specifically, it has no effect on command line tools (which I put in a commands subdirectory). Looks like it works for libraries (which I put in a lib/ subdirectory).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm using VS Code to write command-line tools that use KV, which is currently an unstable API.
For these files, the only way I know to get VS Code to type-check unstable API's is to add this to the top of each file:
Supposedly, setting vscode.unstable to true in .vscode/settings.json should do it, but I've never been able to get it to work.
Specifically, it has no effect on command line tools (which I put in a commands subdirectory). Looks like it works for libraries (which I put in a lib/ subdirectory).
Has anyone else seen this work? Some kind of bug?
Beta Was this translation helpful? Give feedback.
All reactions