2.2 KiB
LSP Extensions
This document describes LSP extensions used by rust-analyzer.
It's a best effort document, when in doubt, consult the source (and send a PR with clarification ;-) ).
We aim to upstream all non Rust-specific extensions to the protocol, but this is not a top priority.
All capabilities are enabled via experimental field of ClientCapabilities.
SnippetTextEdit
Client Capability: { "snippetTextEdit": boolean }
If this capability is set, WorkspaceEdits returned from codeAction requests might contain SnippetTextEdits instead of usual TextEdits:
interface SnippetTextEdit extends TextEdit {
insertTextFormat?: InsertTextFormat;
}
export interface TextDocumentEdit {
textDocument: VersionedTextDocumentIdentifier;
edits: (TextEdit | SnippetTextEdit)[];
}
When applying such code action, the editor should insert snippet, with tab stops and placeholder.
At the moment, rust-analyzer guarantees that only a single edit will have InsertTextFormat.Snippet.
Example
"Add derive" code action transforms struct S; into #[derive($0)] struct S;
Unresolved Questions
- Where exactly are
SnippetTextEdits allowed (only in code actions at the moment)? - Can snippets span multiple files (so far, no)?
joinLines
Server Capability: { "joinLines": boolean }
This request is send from client to server to handle "Join Lines" editor action.
Method: experimental/JoinLines
Request:
interface JoinLinesParams {
textDocument: TextDocumentIdentifier,
/// Currently active selections/cursor offsets.
/// This is an array to support multiple cursors.
ranges: Range[],
}
Response:
TextEdit[]
Example
fn main() {
/*cursor here*/let x = {
92
};
}
experimental/joinLines yields (curly braces are automagiacally removed)
fn main() {
let x = 92;
}
Unresolved Question
- What is the position of the cursor after
joinLines? Currently this is left to editor's discretion, but it might be useful to specify on the server via snippets. However, it then becomes unclear how it works with multi cursor.