Zed LSP Client support for deno-lsp code action commands (workspace/executeCommand)

[notpeter]

I wanted to document various LSPs and the commands they expose as Code Actions, but require coordination from the LSP client (Zed) to actual implement. Currently Zed does not support workspace/executeCommand. There is some active work in zed-industries/zed#16746 but nothing yet. Assuming that work lands, there will still be additional work necessary to expose these via the zed extensions_api.

Commands in Deno LSP Docs:

Commands

There are several commands that might be issued by the language server to the client, which the client is expected to implement:

.cache

deno.cache is sent as a resolution code action when there is an un-cached module specifier that is being imported into a module. It will be sent with and argument that contains the resolved specifier as a string to be cached.

showReferences

deno.showReferences is sent as the command on some code lenses to show locations of references. The arguments contain the specifier that is the subject of the command, the start position of the target and the locations of the references to show.

test

deno.test is sent as part of a test code lens to, of which the client is expected to run a test based on the arguments, which are the specifier the test is contained in and the name of the test to filter the tests on.

Anyways, I wanted to document these limitations of the Zed and thus the Zed Deno experience.
👍 and subscribe if you'd like to be notified of any updates for this.