aboutsummaryrefslogtreecommitdiff
path: root/editors/code/src/commands
Commit message (Collapse)AuthorAgeFilesLines
...
* Rich mapping of cargo watch outputRyan Cumming2019-06-251-54/+132
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-242-5/+11
|
* Fix tslintsAleksei Sidorov2019-06-241-3/+1
|
* Introduce cargo-watch.check-commandAleksei Sidorov2019-06-242-5/+9
|
* Pass `--all-targets` to `cargo watch`Aleksi Juvani2019-05-211-1/+1
|
* switch to official extend selection APIAleksey Kladov2019-04-212-36/+0
|
* start cargo watch if not started interactivelyBernardo2019-04-191-1/+11
|
* cargo watch start and stop commandsBernardo2019-04-193-53/+74
|
* Sends cwd info for runnables and code lensesRoberto Vidal2019-04-141-1/+2
|
* 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
|
* Add Cargo.toml file check before cargo watch startEdwin Cheng2019-04-021-0/+22
|
* Add cargo-watch.check-argumentsEdwin Cheng2019-04-022-28/+66
|
* Add config for cargo-watch traceEdwin Cheng2019-04-022-9/+36
|
* Add proper process teminate methodEdwin Cheng2019-04-022-8/+10
|
* Fix prettier errorEdwin Cheng2019-04-023-21/+30
|
* Fixed tslint errorEdwin Cheng2019-04-021-1/+1
|
* Fix tslint errorEdwin Cheng2019-04-022-63/+65
|
* Improve cargo-watch usageEdwin Cheng2019-04-022-22/+175
|
* Don't execute cargo watch when popup is dismissedpcpthm2019-03-221-2/+2
|
* Change enableCargoWatchOnStartup to have three statesVille Penttinen2019-03-211-10/+13
| | | | | | | 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-181-0/+4
|
* Separate out the interactive cargo watch procedureIgor Matuszewski2019-03-181-1/+67
|
* Reformat using PrettierIgor Matuszewski2019-03-181-5/+5
|
* Respect the user-provided label when creating taskIgor Matuszewski2019-03-181-1/+1
|
* Define a cargo watch taskIgor Matuszewski2019-03-181-1/+21
|
* Remove redundant Runnable.rangeIgor Matuszewski2019-03-181-1/+0
|
* Rename syntaxtree text provider to SyntaxTreeContentProviderVille Penttinen2019-03-031-2/+2
|
* Add vscode support for range in SyntaxTreeParamsVille Penttinen2019-03-031-9/+35
| | | | | | This enables the client to use a command to either show the live-updating version of the syntax tree for the current file. Or optionally when a selected range is provided, we then provide a snapshot of the syntax tree for the range.
* Clear the console when running single taskskjeremy2019-01-301-1/+2
|
* align command namingAleksey Kladov2019-01-288-11/+14
|
* better statsAleksey Kladov2019-01-251-6/+55
|
* ad status commandAleksey Kladov2019-01-222-0/+14
|
* Prettier fixAlan Du2019-01-151-1/+4
|
* Reveal the newly added source change in the editor.Jeremy A. Kolb2019-01-141-0/+1
|
* npm fix runJeremy Kolb2019-01-123-7/+12
|
* Move run_single into runnablesJeremy Kolb2019-01-123-65/+16
|
* Code lens support for running testsJeremy A. Kolb2019-01-112-0/+65
|
* fix open of created or renamed fileBernardo2019-01-051-1/+2
|
* use lsp WorkspaceEdit instead of custom source_file_edits and file_system_editsBernardo2019-01-031-33/+10
|
* use new clear-terminal featureAleksey Kladov2018-12-151-2/+2
|
* Remove uneeded charactersDJMcNab2018-12-081-3/+3
|
* Fix on enterAdolfo Ochagavía2018-11-091-2/+2
|
* Rename File -> SourceFileNodeAleksey Kladov2018-11-071-2/+2
|
* Fully add inline modules to module treeAleksey Kladov2018-11-052-9/+8
|
* Format vscode extension and add npm run fixAdolfo Ochagavía2018-10-092-6/+15
|
* Add on-enter handlerAleksey Kladov2018-10-092-1/+32
| | | | Now, typing doc comments is much more pleasant
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-17 02:23:41 +0000