aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src/client.ts
Commit message (Collapse)AuthorAgeFilesLines
* More robust status notificationsAleksey Kladov2021-04-061-1/+1
|
* Remove Semantic Tokens flicker workaroundkjeremy2021-02-161-17/+0
| | | | | https://github.com/microsoft/vscode-languageserver-node/issues/576 has been closed with the latest vscode-languageclient release.
* Start LSP 3.17 supportJeremy Kolb2021-02-141-1/+1
|
* fix errorsSahandevs2021-02-071-1/+1
|
* handle promise catchesSahandevs2021-02-071-1/+1
|
* remove unnecessarySahandevs2021-02-071-1/+1
|
* Add an option for extra env vars in the Code extensionlf-2020-12-301-2/+9
|
* Use vscode-languageclient 7.0.0-next.14kjeremy2020-11-171-0/+2
|
* Switch to upstream protocol for resolving code actionAleksey Kladov2020-11-101-9/+12
| | | | | | Note that we have to maintain custom implementation on the client side: I don't see how to marry bulitin resolve support with groups and snippets.
* Restore semantic token flickering workaround removed in #5697Charles Pierce2020-11-041-0/+17
|
* Move to vscode-languageclient 7.0.0-next.9kjeremy2020-09-021-12/+3
| | | | Stabilizes call hierarchy and semantic tokens features.
* Remove 'as any'Jeremy Kolb2020-08-091-1/+1
|
* Remove workaround for semantic token flickeringJeremy Kolb2020-08-091-7/+1
| | | | | | See: https://github.com/microsoft/vscode-languageserver-node/issues/576#issuecomment-593384479 This has been fixed since vscode 1.44
* ProblemMatcher auto detects relative/absolute paths and matches VSCode LSP's ↵James Leitch2020-07-231-0/+1
| | | | owner and source. VSCode LSP updated to specify owner.
* Pass CodeActionKind through our middleware to populate menusJeremy Kolb2020-07-021-2/+4
|
* Implement StatusBarAleksey Kladov2020-07-021-0/+1
|
* Remove hover contents marking as trusted.vsrs2020-06-051-15/+2
| | | | | Hover contents might be extracted from raw doc comments and need some validation.
* Add hover actions LSP extension documentation.vsrs2020-06-051-1/+1
|
* Add hover actions as LSP extensionvsrs2020-06-051-0/+45
|
* Fix review commentsMikhail Rakhmanov2020-06-031-2/+0
|
* Preliminary implementation of lazy CodeAssitsMikhail Rakhmanov2020-06-021-36/+40
|
* CodeAction groupsAleksey Kladov2020-05-221-4/+37
|
* Implement client-side of SnippetTextEditAleksey Kladov2020-05-191-2/+46
|
* Add snippetTextEdit protocol extensionAleksey Kladov2020-05-191-4/+15
|
* Merge #4145bors[bot]2020-04-251-29/+0
|\ | | | | | | | | | | | | | | | | | | | | 4145: Remove dead code r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * Remove dead codeAleksey Kladov2020-04-251-29/+0
| |
* | Remove unnecessary async from vscode language client creationveetaha2020-04-251-1/+1
|/
* Enable the SemanticTokensFeature by defaultkjeremy2020-04-081-10/+6
| | | | | | | This is covered under vscode's "editor.semanticHighlighting.enabled" setting plus the user has to have a theme that has opted into highlighting. Bumps required vscode stable to 1.44
* Lean onto default implementation of configsAleksey Kladov2020-04-021-25/+1
|
* Remove old syntax highlightingAleksey Kladov2020-04-021-1/+0
|
* Pass string instread of WorkspaceFolderTim2020-03-311-2/+2
|
* Throw error if no folder is openedTim2020-03-311-2/+2
|
* Add basic task supportTim2020-03-301-3/+2
| | | | This adds basic support for running `cargo build`, `cargo run`, etc.
* Code review fixesKirill Bulatov2020-03-301-1/+1
| | | | Co-Authored-By: Veetaha <[email protected]>
* Style fixesKirill Bulatov2020-03-301-2/+2
|
* Send the config from the clientKirill Bulatov2020-03-301-23/+26
|
* Extension types and renderingMatt Hooper2020-03-241-0/+1
|
* Don't try to enable proposed API's on stableAleksey Kladov2020-03-241-2/+4
|
* Remove unused config from VSCode extEmil Lauridsen2020-03-171-1/+0
|
* Merge #3561 #3577bors[bot]2020-03-131-0/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3561: feat: add debug code lens r=matklad a=hdevalke Refs #3539 3577: Protect against infinite macro expansion in def collector r=edwin0cheng a=flodiebold Something I noticed while trying to make macro expansion more resilient against errors. There was a test for this, but it wasn't actually working because the first recursive expansion failed. (The comma...) Even with this limit, that test (when fixed) still takes some time to pass because of the exponential growth of the expansions, so I disabled it and added a different one without growth. CC @edwin0cheng Co-authored-by: Hannes De Valkeneer <[email protected]> Co-authored-by: hdevalke <[email protected]> Co-authored-by: Florian Diebold <[email protected]>
| * fixup! feat: add debug code lensHannes De Valkeneer2020-03-121-0/+1
| | | | | | | | autodetect vscode-lldb
* | Simpler deserializationAleksey Kladov2020-03-121-1/+6
| |
* | Merge #3543bors[bot]2020-03-121-1/+1
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | 3543: Parameter inlay hint separate from variable type inlay? #2876 r=matklad a=slyngbaek Add setting to allow enabling either type inlay hints or parameter inlay hints or both. Group the the max inlay hint length option into the object. - Add a new type for the inlayHint options. - Add tests to ensure the inlays don't happen on the server side Co-authored-by: Steffen Lyngbaek <[email protected]>
| * Switch from Vec<InlayKind> to object with propsSteffen Lyngbaek2020-03-121-1/+1
| | | | | | | | | | | | | | - Instead of a single object type, use several individual nested types to allow toggling from the settings GUI - Remove unused struct definitions - Install and test that the toggles work
| * Parameter inlay hint separate from variable type inlay? #2876Steffen Lyngbaek2020-03-101-1/+1
| | | | | | | | | | | | | | | | | | Add setting to allow enabling either type inlay hints or parameter inlay hints or both. Group the the max inlay hint length option into the object. - Add a new type for the inlayHint options. - Add tests to ensure the inlays don't happen on the server side
* | Add additional_outdirs in configEdwin Cheng2020-03-101-0/+1
|/
* Fix lintAleksey Kladov2020-02-271-1/+1
|
* Fix flickering with new syntax highlightingAleksey Kladov2020-02-271-1/+9
|
* Config to switch to semantic tokensAleksey Kladov2020-02-261-2/+5
|
* Enable SemanticTokens on the clientJeremy Kolb2020-02-261-0/+3
| | | | This will crash the extension on stable and insiders without the "--enable-proposed-api matklad.rust-analyzer" command line switch.