Opening 'virtual' LSP definitions

Hello again. I’m building an extension against the Deno LSP. Getting code definitions for local files works, but getting definitions for external modules doesn’t.

The Deno LSP sends back targetUris that look like this: deno:/https/deno.land/x/vscode_languageserver_types%40v0.1.0/mod.ts. The idea is that you then send a deno/virtualTextDocument request to the Deno LSP, which returns a string you can open up in the editor.

Given that there’s no way to override the built-in handling of this LSP request, what would be the best way to proceed? Lobby for a way to override Nova’s default language client handling?

2 Likes

I’ve recently begun to contribute to the Deno extension, and we’re looking into features which would benefit from this capability. It would be great that it were added.