vscode deno doesn't auto discover deno.json when its in a subdirectory

[ry]

I have a mutli-language project structure where the deno.json is actually in a sub-directory. The lsp and/or vscode extension doesn't auto discover the deno.json which leads to red squiggles on my imports when using an import map.

By changing the .vscode/settings.json I can work around this:

{
  "rust-analyzer.cargo.features": [
    "e2e_tests"
  ],
  "deno.enable": true,
  "deno.config": "./drg/deno.json",
  "deno.enablePaths": ["./drg"]
}

However I expect many users will get stuck here.

I suggest that each time we see a TS or JS file we walk up the tree towards the root looking for deno.json.

Note: we don't support multiple config files yet denoland/vscode_deno#787

[nayeemrmn]

Subdirectory detection will probably be coupled with multi-root detection. Closing in favour of denoland/vscode_deno#787.

[CITIZENDOT]

How is #787 related to this issue?

[nayeemrmn]

How is #787 related to this issue?

Sorry, edited.

[nayeemrmn]

Actually let's keep this open alongside denoland/vscode_deno#787.