aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src/rust-analyzer-api.ts
Commit message (Collapse)AuthorAgeFilesLines
* Document matchingBrace LSP requestAleksey Kladov2020-05-241-4/+3
|
* Use WorkspaceEdit for ssrAleksey Kladov2020-05-211-1/+1
|
* Formalize JoinLines protocol extensionAleksey Kladov2020-05-211-2/+2
|
* Transition OnEnter to WorkspaceSnippetEditAleksey Kladov2020-05-211-1/+1
| | | | | | | | This also changes our handiling of snippet edits on the client side. `editor.insertSnippet` unfortunately forces indentation, which we really don't want to have to deal with. So, let's just implement our manual hacky way of dealing with a simple subset of snippets we actually use in rust-analyzer
* Extension types and renderingMatt Hooper2020-03-241-1/+3
|
* Merge #3540bors[bot]2020-03-161-1/+2
|\ | | | | | | | | | | | | | | 3540: Swtches to rust SSR query check r=matklad a=mikhail-m1 related to #3186 Co-authored-by: Mikhail Modin <[email protected]>
| * Swtches to rust SSR query checkMikhail Modin2020-03-151-1/+2
| |
* | feat: add debug code lensHannes De Valkeneer2020-03-111-2/+1
|/ | | | Refs #3539
* vscode: redesign inlay hints to be capable of handling multiple editorsVeetaha2020-03-071-2/+2
|
* vscode: extract Type and Param hint cases of InlayHint at type level (needed ↵Veetaha2020-03-071-8/+14
| | | | further)
* vscode: migrate rust-analyzer-api to import * as lc as per matklad and kjeremyVeetaha2020-02-241-23/+23
|
* vscode: create rust-analyzer-api.tsVeetaha2020-02-241-0/+117