aboutsummaryrefslogtreecommitdiff
path: root/editors
Commit message (Collapse)AuthorAgeFilesLines
* Fix SSR prompt following #4919David Lattimore2020-06-271-1/+1
|
* Merge #5017bors[bot]2020-06-266-83/+104
|\ | | | | | | | | | | | | | | | | | | | | | | 5017: Add custom cargo runners support. r=matklad a=vsrs This PR adds an option to delegate actual cargo commands building to another extension. For example, to use a different manager like [cross](https://github.com/rust-embedded/cross). https://github.com/vsrs/cross-rust-analyzer is an example of such extension. I'll publish it after the rust-analyzer release with this functionality. Fixes https://github.com/rust-analyzer/rust-analyzer/issues/4902 Co-authored-by: vsrs <[email protected]>
| * Fix ts lintsvsrs2020-06-241-2/+2
| |
| * Switch to ShellExecution instead of full Taskvsrs2020-06-242-41/+45
| |
| * Add custom cargo runnersvsrs2020-06-246-56/+73
| |
* | Merge branch 'Veetaha-feat/sync-branch'Aleksey Kladov2020-06-252-103/+0
|\ \
| * | Migrate flycheck to fully-lsp-compatible progress reports (introduce ↵veetaha2020-06-182-103/+0
| | | | | | | | | | | | ra_progress crate)
* | | Merge #5025bors[bot]2020-06-241-57/+27
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 5025: Don't mess with messy temp dir and just download into extension dir r=matklad a=Veetaha Temp dirs are messy. Dealing with them requires handling quite a bunch of edge cases. As proposed by lnicola this seems better to just put the temp files in the extension dir and not care much about suddenly leaving garbage. Instead we get shorter and less platform-caveat-y code. We will also assume users don't try to issue a download in different vscode windows simultaneously. Fixes #5019 Co-authored-by: Veetaha <[email protected]>
| * | | Append 10 random hex chars to temp artifact filesVeetaha2020-06-241-1/+5
| | | |
| * | | Don't mess with messy temp dir and just download into extension dirVeetaha2020-06-241-57/+23
| | |/ | |/| | | | | | | | | | | | | | | | | | | Temp dirs are messy. Dealing with them requires handling quite a bunch of edge cases. As proposed by lnicola this seems better to just put the temp files in the extension dir and not care much about suddenly leaving garbage. Instead we get shorter and less platform-caveat-y code. We will also assume users don't try to issue a download in different vscode windows simultaneously
* / | Remove namedExports configLaurențiu Nicola2020-06-241-6/+1
|/ /
| |
| \
| \
| \
| \
| \
*-----. \ Merge #4992 #4993 #4994 #4997 #4998bors[bot]2020-06-234-50/+66
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4992: Never disable error logging on the frontend r=matklad a=Veetaha 4993: Make bootstrap error message more informative and better-fitting r=matklad a=Veetaha Now this better fits standard vscode extension activation failure message and suggests enabling verbose logs. ![image](https://user-images.githubusercontent.com/36276403/85321828-ffbb9400-b4cd-11ea-8adf-4032b1f62dfd.png) 4994: Decouple http file stream logic from temp dir logic r=matklad a=Veetaha Followup for #4989 4997: Update manual.adoc r=matklad a=gwutz GNOME Builder (Nightly) supports now rust-analyzer 4998: Disrecommend trace.server: "verbose" for regular users r=matklad a=Veetaha This option has never been useful for me, I wonder if anyone finds regular users can use this for sending logs Co-authored-by: Veetaha <[email protected]> Co-authored-by: Günther Wagner <[email protected]>
| | | | * | Disrecommend trace.server: "verbose" for regular usersVeetaha2020-06-221-1/+1
| |_|_|/ / |/| | | |
| | | * | Decouple http file stream logic from temp dir logicVeetaha2020-06-222-44/+57
| |_|/ / |/| | |
| | * | Make bootstrap error message more informative and better-fittingVeetaha2020-06-221-4/+8
| | | |
| * | | Never disable error logging on the frontendVeetaha2020-06-221-1/+0
|/ / /
* / / Hotfix skipping the first chunks of the artifactsVeetaha2020-06-221-6/+7
|/ /
* | Download artifacts into tmp dirVeetaha2020-06-202-11/+60
| |
* | Update workaround commentVeetaha2020-06-191-3/+2
| |
* | Add `rust-analyzer.gotoLocation` commandvsrs2020-06-184-0/+23
| |
* | Fix rust-analyzer.debug.openDebugPane optionvsrs2020-06-182-2/+2
|/
* Warnings as hint or infoGabriel Valfridsson2020-06-161-0/+18
|
* checkOnSafe.features and checkOnSafe.allFeatures now work identically.Clemens Wasser2020-06-101-2/+5
|
* Most of the checkOnSafe options now default to the cargo equivalent.Clemens Wasser2020-06-101-4/+7
|
* Added the rust-analyzer.checkOnSave.features option.Clemens Wasser2020-06-101-0/+8
|
* Merge #4773bors[bot]2020-06-081-0/+10
|\ | | | | | | | | | | | | | | | | | | 4773: Run|Debug hover actions. r=matklad a=vsrs ![hover_actions_run](https://user-images.githubusercontent.com/62505555/83335644-dfc1f780-a2b6-11ea-820b-ccaa82290e7d.gif) This hover actions work exactly like corresponding lenses. Co-authored-by: vsrs <[email protected]>
| * Add Run|Debug hover actionsvsrs2020-06-061-0/+10
| |
* | Fix VSCode settingsVincent Isambart2020-06-071-4/+1
|/
* Fix Run lens.vsrs2020-06-061-1/+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-054-7/+79
|
* Merge branch 'master' into compute-lazy-assitsMikhail Rakhmanov2020-06-031-0/+19
|\ | | | | | | | | | | # Conflicts: # crates/rust-analyzer/src/main_loop/handlers.rs # crates/rust-analyzer/src/to_proto.rs
| * Document rust-project.jsonAleksey Kladov2020-06-031-0/+19
| |
* | Fix review commentsMikhail Rakhmanov2020-06-032-3/+0
| |
* | Merge remote-tracking branch 'upstream/master' into compute-lazy-assitsMikhail Rakhmanov2020-06-024-23/+31
|\| | | | | | | | | # Conflicts: # crates/rust-analyzer/src/to_proto.rs
| * Merge #4710bors[bot]2020-06-023-21/+29
| |\ | | | | | | | | | | | | | | | | | | | | | 4710: New runnables r=matklad a=matklad bors d=@vsrs Co-authored-by: Aleksey Kladov <[email protected]>
| | * Spec better runnablesAleksey Kladov2020-06-021-1/+1
| | |
| | * New runnables APIAleksey Kladov2020-06-023-20/+28
| | |
| * | Merge #4711bors[bot]2020-06-021-2/+2
| |\ \ | | |/ | |/| | | | | | | | | | | | | | | | 4711: Disable rust-analyzer.{cargo,checkOnSave}.allFeatures by default r=matklad a=lnicola Co-authored-by: Laurențiu Nicola <[email protected]>
| | * Disable rust-analyzer.{cargo,checkOnSave}.allFeatures by defaultLaurențiu Nicola2020-06-021-2/+2
| | |
* | | Preliminary implementation of lazy CodeAssitsMikhail Rakhmanov2020-06-024-38/+65
|/ /
* | Move run commands to commands.tsAleksey Kladov2020-06-023-133/+134
| |
* | Merge #4580bors[bot]2020-06-027-59/+107
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | 4580: Fix invoking cargo without consulting CARGO env var or standard installation paths r=matklad a=Veetaha Followup for #4329 The pr essentially fixes [this bug](https://youtu.be/EzQ7YIIo1rY?t=2189) cc @lefticus Co-authored-by: veetaha <[email protected]>
| * Change Runnable.bin -> Runnable.kindveetaha2020-05-317-59/+104
| | | | | | | | | | | | As per matklad, we now pass the responsibility for finding the binary to the frontend. Also, added caching for finding the binary path to reduce the amount of filesystem interactions.
| * Fix invoking cargo without consulting CARGO or standard installation pathsveetaha2020-05-312-4/+7
| |
* | Always derive from `process.env` when spawning a child process/shell executionAlin Sinpalean2020-05-311-1/+1
|/ | | | | | | | | | This is useful when an extension (e.g. Nix Environment Selector) or launch configuration sets one or more environment variables. When `env` is not explicitly specified in the options passed to `child_process.spawn()` or `vscode.ShellExecution()`, then `process.env` gets applied automatically. But when an explicit `env` is set, it should inherit from `process.env` rather than replace it completely.
* Add `inRustProject` when-clause for commands.vsrs2020-05-273-1/+76
|
* Merge #4625 #4629bors[bot]2020-05-271-4/+5
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 4625: Partially fix displaying inlay hints in Github PR diff views r=matklad a=Veetaha See the comment in https://github.com/rust-analyzer/rust-analyzer/issues/4608#issuecomment-63424257 It partially fixes the left side of diff view (the one where old code is displayed), but the diff editor with new code changes still has `file` scheme and will proceed displaying inlay hints... 4629: Fix the `should_panic` snippet r=matklad a=eminence Closes #4628 Co-authored-by: veetaha <[email protected]> Co-authored-by: Andrew Chin <[email protected]>
| * Partially fix displaying inlay hints in Github PR diff viewsveetaha2020-05-261-4/+5
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-13 01:26:02 +0000