aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src/client.ts
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* Push IO and error handling upAleksey Kladov2020-02-171-5/+1
|
* Add arguments to rustfmtIlya Titkov2020-02-171-0/+1
|
* vscode: add version and storage parameters to github binary sourceVeetaha2020-02-161-1/+1
|
* vscode: renamed langServer to serverVeetaha2020-02-141-4/+4
|
* vscode: renmed ArtifactMetadata -> ArtifactReleaseInfo, languageServer -> ↵Veetaha2020-02-141-2/+2
| | | | langServer
* Merge #3131bors[bot]2020-02-141-10/+12
|\ | | | | | | | | | | | | | | 3131: vscode: simplified config and to removed one source of truth of default values r=matklad a=Veetaha Though not intended initially, the implementation of config design is alike [dart's one](https://github.com/Dart-Code/Dart-Code/blob/master/src/extension/config.ts) as pointed by @matklad in PM. Co-authored-by: Veetaha <[email protected]>
| * vscode: moved to getters as per matkladVeetaha2020-02-141-9/+9
| |
| * vscode: redesigned config with simplicity and Dart extension config ↵Veetaha2020-02-131-17/+19
| | | | | | | | implementation in mind
* | Do not register all proposed featureskjeremy2020-02-141-1/+6
|/ | | | | | | | | | | Instead only opt-in to CallHierarchy since it has a vscode API but LSP support is still proposed. Discovered while working on SemanticTokens which does not have a vscode API and is still in the proposed state. Somehow enabling it would crash the language server. See https://github.com/microsoft/vscode-languageserver-node/issues/572
* vscode: refactor platform artifact name query to switch statement, move ↵Veetaha2020-02-081-1/+1
| | | | BinarySource union variants into a namespace
* vscode: amended config to use binary from globalStoragePath, added ui for ↵Veetaha2020-02-081-17/+5
| | | | downloading
* vscode: yet another refactor commitVeetaha2020-02-041-17/+12
|
* vscode extension: migrate from any to unknown where possibleVeetaha2020-02-021-1/+1
|
* Provide better diagnostics if the server is not in pathAleksey Kladov2020-01-281-1/+7
|
* Sanity check for missing server binaryAleksey Kladov2019-12-311-0/+4
|
* Add semicolonsAleksey Kladov2019-12-311-1/+1
|
* Refactor server lifecycleAleksey Kladov2019-12-311-0/+90
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-10 04:40:33 +0000