aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src
Commit message (Collapse)AuthorAgeFilesLines
* Remove vscode_lldb settingAleksey Kladov2020-04-021-0/+4
|
* Lean onto default implementation of configsAleksey Kladov2020-04-024-54/+7
|
* vscode: postrefactorveetaha2020-04-021-12/+6
|
* vscode: postrefactor variable namesveetaha2020-04-021-8/+8
|
* vscode: add goto definition from rust file to syntax tree editorveetaha2020-04-021-5/+83
|
* Merge #3820bors[bot]2020-04-024-262/+0
|\ | | | | | | | | | | | | | | | | | | | | 3820: Remove old syntax highlighting r=matklad a=matklad bors r+ 🤖 Co-authored-by: Aleksey Kladov <[email protected]>
| * Remove old syntax highlightingAleksey Kladov2020-04-024-262/+0
| |
* | 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
*-. Merge #3780 #3787bors[bot]2020-03-312-54/+115
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 3780: Simplify r=matklad a=Veetaha I absolutely love tha fact that removing `.clone()` simplifies the code comparing to other languages where it's actually the contrary (ahem ~~`std::move()`~~) 3787: vscode: add syntax tree inspection hovers and highlights r=matklad a=Veetaha ![inspect-tree](https://user-images.githubusercontent.com/36276403/78029767-c7426900-7369-11ea-9ed6-b8a0f8e05bac.gif) I implemented the reverse mapping (when you hover in the rust editor), but it seems overcomplicated, so I removed it Related #3682 Co-authored-by: veetaha <[email protected]> Co-authored-by: Veetaha <[email protected]>
| | * 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-312-55/+118
| |/
* | Pass string instread of WorkspaceFolderTim2020-03-313-5/+5
| |
* | Remove unnecessary null checkTim2020-03-311-3/+1
| |
* | Throw error if no folder is openedTim2020-03-313-4/+9
| |
* | Use namespace importTim2020-03-311-19/+11
| |
* | Add basic task supportTim2020-03-304-6/+77
|/ | | | This adds basic support for running `cargo build`, `cargo run`, etc.
* Code review fixesKirill Bulatov2020-03-303-6/+8
| | | | Co-Authored-By: Veetaha <[email protected]>
* Style fixesKirill Bulatov2020-03-303-5/+7
|
* Send the config from the clientKirill Bulatov2020-03-302-24/+28
|
* Process configuration response draftKirill Bulatov2020-03-301-3/+3
|
* Client side draftKirill Bulatov2020-03-301-0/+6
|
* 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
|
* Merge #3725bors[bot]2020-03-262-23/+21
|\ | | | | | | | | | | | | | | 3725: vscode: fix local devel and remove disposables memory leak on server restrart r=matklad a=Veetaha Co-authored-by: veetaha <[email protected]>
| * vscode: small post-refactorveetaha2020-03-261-3/+1
| |
| * vscode: fix memory leak on server restartveetaha2020-03-261-15/+13
| | | | | | | | The memory leak was because on the server restrart the array of extensionContext.substiptions was not cleared
| * vscode: fix local develveetaha2020-03-262-5/+7
| | | | | | | | The value of releaseTag is not undefined, but null in actual package.json
* | Merge #3726bors[bot]2020-03-261-20/+11
|\ \ | |/ |/| | | | | | | | | | | 3726: vscode: refactor analyzer status r=matklad a=Veetaha Co-authored-by: veetaha <[email protected]>
| * vscode: refactor analyzer statusveetaha2020-03-251-20/+11
| |
* | Use the right arch name for x86 (32 bit)Aleksey Kladov2020-03-251-1/+1
| |
* | Extension types and renderingMatt Hooper2020-03-244-4/+34
| |
* | Merge #3695bors[bot]2020-03-241-61/+45
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | 3695: vscode: simplify and refactor config r=matklad a=Veetaha Removed unnecessary interfaces, changed `cfg` to be a getter to ensure the fresh values any time possible. Migrated from explicit casts to implicit. Co-authored-by: veetaha <[email protected]>
| * | vscode: simplify and refactor configveetaha2020-03-231-61/+45
| |/
* / Don't try to enable proposed API's on stableAleksey Kladov2020-03-243-21/+17
|/
* vscode: remove unnecessary codeVeetaha2020-03-201-2/+0
| | | This cancel is unnecessary since we cancel the previous inlay hints requests in `fetchHints()` method itself. This is not a hard error, we just called cancel() 2 times.
* Make from-source install use cargo installed binary by defaultAleksey Kladov2020-03-202-2/+4
|
* Simplify extension tag sniffingAleksey Kladov2020-03-192-15/+9
|
* Rewrite auto-updateAleksey Kladov2020-03-1911-690/+263
| | | | | | | | | | | | | | 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).
* Remove outDirOverridesEmil Lauridsen2020-03-171-2/+0
|
* Remove unused config from VSCode extEmil Lauridsen2020-03-171-1/+0
|
* Change existing OUT_DIR override config to make use of new infrastructureEmil Lauridsen2020-03-171-1/+2
|
* Support loading OUT_DIR from cargo check at launchEmil Lauridsen2020-03-171-0/+3
|
* Separate persistent mutable state from configAleksey Kladov2020-03-167-65/+80
| | | | | That way, we clearly see which things are not change, and we also clearly see which things are persistent.
* Merge #3534bors[bot]2020-03-1610-144/+419
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-postrefactor: migrate to arrow functionsVeetaha2020-03-161-2/+2
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-30 04:03:17 +0100