aboutsummaryrefslogtreecommitdiff
path: root/editors/code
Commit message (Collapse)AuthorAgeFilesLines
...
* Rich mapping of cargo watch outputRyan Cumming2019-06-252-54/+352
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently we depend on the ASCII rendering string that `rustc` provides to populate Visual Studio Code's diagnostic. This has a number of shortcomings: 1. It's not a very good use of space in the error list 2. We can't jump to secondary spans (e.g. where a called function is defined) 3. We can't use Code Actions aka Quick Fix This moves all of the low-level parsing and mapping to a `rust_diagnostics.ts`. This uses some heuristics to map Rust diagnostics to VsCode: 1. As before, the Rust diagnostic message and primary span is used for the root diagnostic. However, we now just use the message instead of the rendered version. 2. Every secondary span is converted to "related information". This shows as child in the error list and can be jumped to. 3. Every child diagnostic is categorised in to three buckets: 1. If they have no span they're treated as another line of the root messages 2. If they have replacement text they're treated as a Code Action 3. If they have a span but no replacement text they're treated as related information (same as secondary spans).
* Fix code after "apply suggestions"Aleksei Sidorov2019-06-244-15/+21
|
* Apply suggestions from code reviewAleksey Sidorov2019-06-242-4/+4
| | | Co-Authored-By: Aleksey Kladov <[email protected]>
* Fix tslintsAleksei Sidorov2019-06-242-5/+3
|
* Introduce cargo-watch.check-commandAleksei Sidorov2019-06-244-7/+27
|
* make LRU cache configurableAleksey Kladov2019-06-123-1/+11
|
* Make rainbows optionalPascal Hertleif2019-05-273-5/+18
|
* Semantic highlighting spikePascal Hertleif2019-05-273-3/+54
| | | | | | | | | | Very simple approach: For each identifier, set the hash of the range where it's defined as its 'id' and use it in the VSCode extension to generate unique colors. Thus, the generated colors are per-file. They are also quite fragile, and I'm not entirely sure why. Looks like we need to make sure the same ranges aren't overwritten by a later request?
* Improve highlighting of name refsLaurențiu Nicola2019-05-232-2/+52
|
* Address feedbackLaurențiu Nicola2019-05-212-31/+21
|
* Use ThemeColor and add support for light themesLaurențiu Nicola2019-05-212-13/+141
|
* Pass `--all-targets` to `cargo watch`Aleksi Juvani2019-05-211-1/+1
|
* switch to official extend selection APIAleksey Kladov2019-04-215-45/+1
|
* :arrow_up: codeAleksey Kladov2019-04-212-1442/+185
|
* start cargo watch if not started interactivelyBernardo2019-04-193-3/+20
|
* recover rustc-watch problemMatchersBernardo2019-04-191-0/+12
|
* cargo watch start and stop commandsBernardo2019-04-195-55/+100
|
* PrettierRoberto Vidal2019-04-161-2/+1
|
* Fixes unrelated process termination quirkRoberto Vidal2019-04-161-0/+0
|
* Adds "restart server" commandRoberto Vidal2019-04-162-1/+20
|
* Sends cwd info for runnables and code lensesRoberto Vidal2019-04-141-1/+2
|
* Adds support for multiple editor workspaces on initializationRoberto Vidal2019-04-141-7/+0
| | | | This is a quick, partial fix for #1104
* Fix eslint errorsEmil Lauridsen2019-04-031-1/+1
|
* Add extra double quotes only on Windows.Emil Lauridsen2019-04-031-0/+4
| | | | | | As tested by @edwin0cheng, Windows requires the quotes removed in the previous commit. This commit re-adds the quotes gated by an if statement on the node environment, so that quotes are only added on Windows.
* Fix VSCode cargo-watch functionality on Linux.Emil Lauridsen2019-04-031-2/+1
| | | | | | | | | | | | | As of #1079 the VSCode cargo-watch functionality has been broken on Linux systems. The cause seems to be that linux takes the added quotes inside process arguments literally, so it attempts to make cargo-watch run the command `cargo "check --message-format json"` with the entire quoted part being treated as a single long subcommand, which cargo doesn't know how to handle. Removing the extra quotes solves the issue.
* Add cargo-watch package animation and refactoringEdwin Cheng2019-04-022-44/+78
|
* Fix prettier errorEdwin Cheng2019-04-021-1/+1
|
* Add terminate process implemntation noteEdwin Cheng2019-04-021-0/+7
|
* Add Cargo.toml file check before cargo watch startEdwin Cheng2019-04-021-0/+22
|
* Add cargo-watch.check-argumentsEdwin Cheng2019-04-025-74/+137
|
* Add config for cargo-watch traceEdwin Cheng2019-04-024-15/+66
|
* Add proper process teminate methodEdwin Cheng2019-04-026-10/+116
|
* Fix prettier errorEdwin Cheng2019-04-024-22/+31
|
* Fixed tslint errorEdwin Cheng2019-04-021-1/+1
|
* Fix tslint errorEdwin Cheng2019-04-022-63/+65
|
* Improve cargo-watch usageEdwin Cheng2019-04-024-36/+177
|
* Don't execute cargo watch when popup is dismissedpcpthm2019-03-221-2/+2
|
* Change enableCargoWatchOnStartup to have three statesVille Penttinen2019-03-213-16/+31
| | | | | | | This fixes #1005. Defaults to `ask` which prompts users each time whether to start `cargo watch` or not. `enabled` always starts `cargo watch` and `disabled` does not.
* Appease CIIgor Matuszewski2019-03-181-9/+7
|
* Guard auto cargo watch behind a config optionIgor Matuszewski2019-03-183-0/+17
|
* Separate out the interactive cargo watch procedureIgor Matuszewski2019-03-182-64/+70
|
* Reformat using PrettierIgor Matuszewski2019-03-182-17/+35
|
* Remove unused importsIgor Matuszewski2019-03-181-2/+1
|
* Prefer installing `cargo-watch` via Task APIIgor Matuszewski2019-03-181-23/+14
| | | | This gives us much more fine-grained stdout buffering and ANSI terminal colors.
* Respect the user-provided label when creating taskIgor Matuszewski2019-03-181-1/+1
|
* Ask the user to install and start cargo watchIgor Matuszewski2019-03-181-5/+61
|
* Define a cargo watch taskIgor Matuszewski2019-03-181-1/+21
|
* Remove redundant Runnable.rangeIgor Matuszewski2019-03-181-1/+0
|
* activate extension if Cargo.toml is presentAleksey Kladov2019-03-131-1/+2
|
* Applied code style of ``npm run fix``Lucas Spits2019-03-111-6/+4
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-06 21:15:40 +0000