@mattbierner.bsky.social
These commands can trigger other UI flows too, such showing a quick pick. Again though the commands aren't part of the LSP spec so each client may need to implement them
Another option for basic text input is using a snippet workspace edit: github.com/microsoft/vs...
Another option for basic text input is using a snippet workspace edit: github.com/microsoft/vs...
Snippet edit feature by MariaSolOs · Pull Request #1343 · microsoft/vscode-languageserver-node
Adding support for snippet workspace edits.
Closes #724
github.com
May 1, 2025 at 6:51 PM
These commands can trigger other UI flows too, such showing a quick pick. Again though the commands aren't part of the LSP spec so each client may need to implement them
Another option for basic text input is using a snippet workspace edit: github.com/microsoft/vs...
Another option for basic text input is using a snippet workspace edit: github.com/microsoft/vs...
VS Code does this with the `editor.action.rename` command on the code action (microsoft.github.io/language-ser...)
These command ids aren't part of the spec but that one may be common enough to use. Otherwise you can implement your own command for each client
These command ids aren't part of the spec but that one may be common enough to use. Otherwise you can implement your own command for each client
Specification
This document describes the 3.17.x version of the language server protocol. An implementation for node of the 3.17.x version of the protocol can be found here.
microsoft.github.io
May 1, 2025 at 6:46 PM
VS Code does this with the `editor.action.rename` command on the code action (microsoft.github.io/language-ser...)
These command ids aren't part of the spec but that one may be common enough to use. Otherwise you can implement your own command for each client
These command ids aren't part of the spec but that one may be common enough to use. Otherwise you can implement your own command for each client