Symbols exported from a Deno workspace are not considered in LSP workspace

[nounder]

(Basic technical understanding about 'Deno workspace' and a 'Language Server Protocol workspace' are required to understand subtle terms used here.)

---

Consider following project deno.json:

{
  "workspace": [
    "./h3/"
  ]
}

and its friend ./h3/deno.json:

{
  "name": "@nounder/h3",
  "exports": "./mod.ts"
}

When I search for isStatusOk function that is exported in @nounder/h3, LSP doesn't index it:

However, when I start typing function name in context of a import statement, LSP provides correct autocomplete:

It think it is reasonable to make LSP index symbols defined in workspaces.

Version: Deno 2.1.7
Editors: nvim, vscode, cursor

[nounder]

The above is minimal reproducible example.

In my another project, with more complex deno.json, I had to write import statement by hand that points to workspace module identifier. In this case, LSP autocomplete suggests all exports but instead of using workspace module identifier and limit only to module exports, it suggests exports from all workspace files:

Module identifier auto complete for defined workspaces doesn't work at all, even after writing first one in by hand.