aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src
Commit message (Collapse)AuthorAgeFilesLines
* Merge #8951bors[bot]2021-06-144-47/+38
|\ | | | | | | | | | | | | | | 8951: internal: migrate to vscode.FileSystem API r=matklad a=wxb1ank I encountered an error where `bootstrap()` attempts to create a directory with the path `C:\C:\...`. I couldn't find this reported anywhere else. Using the `vscode.FileSystem` API instead of the `fs` one works here. I assume the latter automatically prepends `C:\` to paths whereas the former does not. I don't know if this suggests `vscode.FileSystem` should be used in more places for consistency. Co-authored-by: wxb1ank <[email protected]>
| * Lint toolchain.tswxb1ank2021-06-021-1/+1
| |
| * migrate from `fs` to `vscode.FileSystem` APIwxb1ank2021-06-023-44/+35
| |
| * internal: use vscode.FileSystem API in main.tswxb1ank2021-06-022-5/+5
| |
* | fixMilo2021-06-071-1/+1
| |
* | fixMilo2021-06-061-1/+1
| |
* | when you click status bar icon it now restarts serverMilo2021-06-061-0/+1
| |
* | Add function references hover actionLukas Wirth2021-06-041-0/+1
|/
* Fix opening single filesKirill Bulatov2021-05-311-1/+1
|
* fix: fix shell injection in task spawningAleksey Kladov2021-05-311-6/+6
| | | | closes #9058
* Merge #8995bors[bot]2021-05-264-22/+20
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8995: fix: Create tasks for all workspaces r=matklad a=SomeoneToIgnore Follow-up of https://github.com/rust-analyzer/rust-analyzer/pull/8955#discussion_r637897170 Before: <img width="593" alt="image" src="https://user-images.githubusercontent.com/2690773/119575267-712b5300-bdbf-11eb-833c-f688f7a7dd0f.png"> After: <img width="643" alt="image" src="https://user-images.githubusercontent.com/2690773/119575273-74264380-bdbf-11eb-8283-a78bbcb7346e.png"> This is the first time I've used multiple workspaces feature in VSCode, but so far looks like * opening detached files works * run and debug lens work * Rust Analyzer: Run action works * run task works and now shows tasks for all workspaces * there are no platform-specific changes involved Co-authored-by: Kirill Bulatov <[email protected]>
| * Create tasks for all workspacesKirill Bulatov2021-05-254-22/+20
| |
* | minor: explicitly set the focus to falseAleksey Kladov2021-05-261-0/+4
|/
* fix: cursor position after item move commandEduardo Canellas2021-05-241-1/+1
| | | | closes Item movers need some fixes #8492
* Merge #8955bors[bot]2021-05-243-41/+69
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8955: feature: Support standalone Rust files r=matklad a=SomeoneToIgnore ![standalone](https://user-images.githubusercontent.com/2690773/119277037-0b579380-bc26-11eb-8d77-20d46ab4916a.gif) Closes https://github.com/rust-analyzer/rust-analyzer/issues/6388 Caveats: * I've decided to support multiple detached files in the code (anticipating the scratch files), but I found no way to open multiple files in VSCode at once: running `code *.rs` makes the plugin to register in the `vscode.workspace.textDocuments` only the first file, while code actually displays all files later. Apparently what happens is the same as when you have VSCode open at some workplace already and then run `code some_other_file.rs`: it gets opened in the same workspace of the same VSCode with no server to support it. If there's a way to override it, I'd appreciate the pointer. * No way to toggle inlay hints, since the setting is updated for the workspace (which does not exist for a single file opened) > [2021-05-24 00:22:49.100] [exthost] [error] Error: Unable to write to Workspace Settings because no workspace is opened. Please open a workspace first and try again. * No runners/lens to run or check the code are implemented for this mode. In theory, we can detect `rustc`, run it on a file and run the resulting binary, but not sure if worth doing it at this stage. Otherwise imports, hints, completion and other features work. Co-authored-by: Kirill Bulatov <[email protected]>
| * Fix ts lint errorsKirill Bulatov2021-05-233-8/+8
| |
| * Send detached files info to server via init paramsKirill Bulatov2021-05-233-6/+27
| |
| * Start rust-analyzer server for arbitrary rust filesKirill Bulatov2021-05-233-39/+46
| |
* | fix: can download server binary on windows againAleksey Kladov2021-05-241-1/+1
| | | | | | | | | | | | Closes #8956 See https://github.com/rust-analyzer/rust-analyzer/pull/8951#issuecomment-846716999
* | fix: reveal snippetsAleksey Kladov2021-05-231-0/+3
|/
* More style fixesKirill Bulatov2021-05-232-16/+19
|
* Style fixKirill Bulatov2021-05-232-12/+11
|
* Don't use a deprecated accessorKirill Bulatov2021-05-231-1/+1
|
* Better releaseId namingKirill Bulatov2021-05-232-12/+11
|
* Remove nightly release id from local storage for stable extensionsKirill Bulatov2021-05-232-1/+6
|
* Download nightly extension when configured and run from stable extension versionKirill Bulatov2021-05-231-3/+10
|
* Use `.rs` file ending to get syntax highlightingJonas Schievink2021-05-211-1/+1
|
* Add a "Debug ItemTree" LSP requestJonas Schievink2021-05-213-0/+57
|
* Allow viewing the crate graph in a webviewJonas Schievink2021-05-113-0/+11
|
* Merge #8624bors[bot]2021-04-274-6/+57
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 8624: Automatically detect rust library source file map r=vsrs a=vsrs This PR adds a new possible `rust-analyzer.debug.sourceFileMap` value: ```json { "rust-analyzer.debug.sourceFileMap": "auto" } ``` I did not make it the default because it uses two shell calls (`rustc --print sysroot` and `rustc -V -v`). First one can be slow (https://github.com/rust-lang/rustup/issues/783) Fixes #8619 Co-authored-by: vsrs <[email protected]>
| * Use explicit rustc commit-hashvsrs2021-04-223-3/+15
| | | | | | | | Required for lldb on mac
| * Add special `auto` value for `debug.sourceFileMap`vsrs2021-04-224-25/+35
| |
| * Autodetect rust library source file mapvsrs2021-04-222-2/+31
| |
* | Fix how and when old inlay hint decorations are disposedJorge Mederos Alvarado2021-04-271-16/+33
| |
* | Add option to opt out from smaller inlay hints font sizeJorge Mederos Alvarado2021-04-272-6/+30
|/
* Move cursor position when using item moversJonas Schievink2021-04-132-23/+5
|
* Sacrifice for the semicolon godAleksey Kladov2021-04-062-5/+5
|
* More robust status notificationsAleksey Kladov2021-04-063-34/+24
|
* Use `const` instead of `let`Jonas Schievink2021-03-271-1/+1
|
* Fix handling of multi-cursor snippetsJonas Schievink2021-03-271-5/+5
| | | | | This allows one snippet per TextEdit, multiple in the same TextEdit are still broken
* Improve cursor positioning after movingivan7702021-03-181-1/+14
|
* Fix tsfmt and eslint warningsivan7702021-03-182-4/+4
|
* Remove movable array, improve client codeivan7702021-03-182-2/+6
|
* Item up and down moversivan7702021-03-183-0/+43
|
* Support multiple parents in parentModule in vscode-clientLukas Wirth2021-03-151-9/+15
|
* Merge #7799bors[bot]2021-03-133-9/+50
|\ | | | | | | | | | | | | | | | | | | | | | | | | 7799: Related tests r=matklad a=vsrs ![tests](https://user-images.githubusercontent.com/62505555/109397453-a9013680-7947-11eb-8b11-ac03079f7645.gif) This adds an ability to look for tests for the item under the cursor: function, constant, data type, etc The LSP part is bound to change. But the feature itself already works and I'm looking for a feedback :) Co-authored-by: vsrs <[email protected]>
| * Apply review suggestionsvsrs2021-03-111-4/+1
| |
| * Remove erroneous commentvsrs2021-02-271-1/+1
| |
| * Add progress reportingvsrs2021-02-271-16/+17
| |
| * Add LSP request and VSCode commandvsrs2021-02-273-9/+52
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-17 06:03:44 +0000