aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src/commands
Commit message (Collapse)AuthorAgeFilesLines
* Merge #3817bors[bot]2020-04-021-1/+4
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3817: vscode: highlight syntax tree ro editor r=matklad a=Veetaha Small textmate grammar declaration to make rust-analyzer syntax tree more easily inspectable: Btw, if we change the file extension of our `ra_syntax/test_data/**` files to `.rast` they should be highlighted in vscode too. The colors of the tokens are actually going to be color-theme dependent, or you can customize them via: ```jsonc { "editor.tokenColorCustomizations": { "textMateRules": [ { "scope": "name", "settings": { /* */ } } ] } } ``` ![image](https://user-images.githubusercontent.com/36276403/78204947-99f9d600-74a3-11ea-8315-cb1c87810c7c.png) Related: #3682 Co-authored-by: veetaha <[email protected]>
| * vscode: add highlighting of syntax treeveetaha2020-04-021-1/+4
| |
* | vscode: add support for light themes and color customization for syntax tree ↵veetaha2020-04-011-2/+4
|/ | | | highlights
* vscode: small refactorveetaha2020-03-311-1/+1
|\
| * vscode: apply review nitsVeetaha2020-03-311-1/+1
| |
* | vscode: scroll to the syntax node in rust editor when highlightingveetaha2020-03-311-1/+2
|/
* vscode: use ctx.subscriptions instead of local .disposablesveetaha2020-03-311-15/+12
|
* vscode: add syntax tree inspection hovers and highlightsveetaha2020-03-311-53/+116
|
* vscode: fix release tag retrievalVeetaha2020-03-271-1/+1
| | | Co-Authored-By: Laurențiu Nicola <[email protected]>
* vscode: show release tag with along with the commit hash for RA version commandveetaha2020-03-261-2/+7
|
* vscode: refactor analyzer statusveetaha2020-03-251-20/+11
|
* Rewrite auto-updateAleksey Kladov2020-03-191-13/+3
| | | | | | | | | | | | | | Everything now happens in main.ts, in the bootstrap family of functions. The current flow is: * check everything only on extension installation. * if the user is on nightly channel, try to download the nightly extension and reload. * when we install nightly extension, we persist its release id, so that we can check if the current release is different. * if server binary was not downloaded by the current version of the extension, redownload it (we persist the version of ext that downloaded the server).
* Separate persistent mutable state from configAleksey Kladov2020-03-161-1/+1
| | | | | That way, we clearly see which things are not change, and we also clearly see which things are persistent.
* Merge #3534bors[bot]2020-03-161-2/+1
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3534: Feature: vscode impl nightlies download and installation r=Veetaha a=Veetaha I need to test things more, but the core shape of the code is quite well-formed. The main problem is that we save the release date only for nightlies and there are no means to get the release date of the stable extension (i.e. for this we would need to consult the github releases via a network request, or we would need to somehow save this info into package.json or any other file accessible from the extension code during the deployment step, but this will be very hard I guess). So there is an invariant that the users can install nightly only from our extension and they can't do it manually, because when installing the nightly `.vsix` we actually save its release date to `globalState` Closes: #3402 TODO: - [x] More manual tests and documentation cc @matklad @lnicola Co-authored-by: Veetaha <[email protected]> Co-authored-by: Veetaha <[email protected]>
| * vscode: amend server installation logic to account for nightliesVeetaha2020-03-141-2/+1
| |
* | Merge #3540bors[bot]2020-03-161-7/+9
|\ \ | | | | | | | | | | | | | | | | | | | | | 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-7/+9
| |/
* | fixup! feat: add debug code lensHannes De Valkeneer2020-03-121-6/+1
| | | | | | | | avoid repetition of `--no-run`
* | fixup! feat: add debug code lensHannes De Valkeneer2020-03-121-2/+1
| |
* | feat: add debug code lensHannes De Valkeneer2020-03-111-1/+27
|/ | | | Refs #3539
* Centralize the check for languageId on documentJulien Roncaglia2020-03-021-2/+3
| | | | Also move visibleRustEditors to Ctx
* vscode: run fmtVeetaha2020-02-241-1/+1
|
* vscode: migrate syntax_tree to rust-analyzer-api.tsVeetaha2020-02-241-20/+7
|
* vscode: migrate ssr to rust-analyzer-api.tsVeetaha2020-02-241-11/+5
|
* vscode: migrate runnables to rust-analyzer-api.tsVeetaha2020-02-241-22/+7
|
* vscode: migrate parent_module to rust-analyzer-api.tsVeetaha2020-02-241-7/+3
|
* vscode: migrate on_enter to rust-analyzer-api.tsVeetaha2020-02-241-14/+7
|
* vscode: migrate matching_brace to rust-analyzer-api.tsVeetaha2020-02-241-12/+3
|
* vscode: migrate join_lines to rust-analyzer-api.tsVeetaha2020-02-241-13/+4
|
* vscode: migrate collectGarbage to rust-analyzer-api.tsVeetaha2020-02-241-5/+4
|
* vscode: migrate expand_macro to rust-analyzer-api.tsVeetaha2020-02-241-13/+5
|
* vscode: migrate analyzer_status to rust-analyzer-api.tsVeetaha2020-02-241-4/+2
|
* Don't block onEnter if request failsAleksey Kladov2020-02-241-0/+6
| | | | closes #3286
* Use stdout directlyEdwin Cheng2020-02-211-2/+1
|
* Use ensureServerBinary insteadEdwin Cheng2020-02-211-5/+17
|
* Add trailing newlineEdwin Cheng2020-02-211-1/+2
|
* Improve server version infoEdwin Cheng2020-02-212-0/+10
|
* enforce camel caseAleksey Kladov2020-02-211-2/+2
|
* vscode: press ; to respect semicolonsVeetaha2020-02-172-3/+3
|
* Simplify some more ctorsAleksey Kladov2020-02-173-9/+3
|
* Simplify TS reload logicAleksey Kladov2020-02-171-7/+0
| | | | Fixes #3164
* Init implementation of structural search replaceMikhail Modin2020-02-142-0/+37
|
* Merge #3024bors[bot]2020-02-052-1/+3
|\ | | | | | | | | | | | | | | 3024: vscode: eliminate floating promises and insane amount of resource handle leaks r=matklad a=Veetaha Khm, yeah ... Co-authored-by: Veetaha <[email protected]>
| * vscode: eliminate floating promises and insane amount of resource handle leaksVeetaha2020-02-052-1/+3
| |
* | vscode: yet another refactor commitVeetaha2020-02-041-1/+1
|/
* Merge two if statements into one in editors/code/src/commands/on_enter.ts.Grégoire Geis2020-02-041-1/+1
| | | Co-Authored-By: Veetaha <[email protected]>
* Remove enableEnhancedTyping and type overriding infrastructure.Gregoire Geis2020-02-031-9/+1
|
* Add regular onEnter command, allowing onEnter to be called without ↵Gregoire Geis2020-02-031-18/+33
| | | | overriding the type command.
* vscode: use void where possibleVeetaha2020-02-021-1/+1
|
* vscode extension: migrate from any to unknown where possibleVeetaha2020-02-021-1/+1
|