Open nathanwhit opened 2 hours ago
This is currently intentional, since we assume that the extension won't enable unless there's a deno.json
... I think the problem is we're still promoting "deno.enable": true
. We should have been phasing out the usage of this setting in favour of deno.json
detection.
Edit: I misunderstood the workspace member part
This is currently intentional, since we assume that the extension won't enable unless there's a
deno.json
... I think the problem is we're still promoting"deno.enable": true
. We should have been phasing out the usage of this setting in favour ofdeno.json
detection.
It enables even without "deno.enable": true
because it's part of the workspace, I have
"enable": null,
"disablePaths": [],
"enablePaths": null,
in my language server status, but the LSP is enabled (I assume due to being a workspace member)
I believe the issue is that it's looking for a tsconfig.json
next to the deno.json
, but since we're in a workspace member without a deno.json (the deno.json is in the parent dir) that condition isn't met
Describe the bug We added helper popups in #1166, but they don't seem to trigger if you're in a workspace member with only a
package.json
To Reproduce
Note that the deno extension enables by default, but the prompts don't show up. If you create a deno.json in
my-app
or if you open the workspace root in vscode, they do.Expected behavior
Prompts appear if in a workspace member, even if it doesn't have a
deno.json