| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | Fix comparison of Code Action edit lengths | Ryan Cumming | 2019-06-25 | 1 | -1/+1 | |
| | | | | | | This happened to work because we always produce a single edit but this is obviously dubious. | |||||
| * | Rich mapping of cargo watch output | Ryan Cumming | 2019-06-25 | 2 | -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 Sidorov | 2019-06-24 | 4 | -15/+21 | |
| | | ||||||
| * | Apply suggestions from code review | Aleksey Sidorov | 2019-06-24 | 2 | -4/+4 | |
| | | | | Co-Authored-By: Aleksey Kladov <[email protected]> | |||||
| * | Fix tslints | Aleksei Sidorov | 2019-06-24 | 2 | -5/+3 | |
| | | ||||||
| * | Introduce cargo-watch.check-command | Aleksei Sidorov | 2019-06-24 | 4 | -7/+27 | |
| | | ||||||
| * | make LRU cache configurable | Aleksey Kladov | 2019-06-12 | 3 | -1/+11 | |
| | | ||||||
| * | Make rainbows optional | Pascal Hertleif | 2019-05-27 | 3 | -5/+18 | |
| | | ||||||
| * | Semantic highlighting spike | Pascal Hertleif | 2019-05-27 | 3 | -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 refs | Laurențiu Nicola | 2019-05-23 | 2 | -2/+52 | |
| | | ||||||
| * | Address feedback | Laurențiu Nicola | 2019-05-21 | 2 | -31/+21 | |
| | | ||||||
| * | Use ThemeColor and add support for light themes | Laurențiu Nicola | 2019-05-21 | 2 | -13/+141 | |
| | | ||||||
| * | Pass `--all-targets` to `cargo watch` | Aleksi Juvani | 2019-05-21 | 1 | -1/+1 | |
| | | ||||||
| * | switch to official extend selection API | Aleksey Kladov | 2019-04-21 | 5 | -45/+1 | |
| | | ||||||
| * | :arrow_up: code | Aleksey Kladov | 2019-04-21 | 2 | -1442/+185 | |
| | | ||||||
| * | start cargo watch if not started interactively | Bernardo | 2019-04-19 | 3 | -3/+20 | |
| | | ||||||
| * | recover rustc-watch problemMatchers | Bernardo | 2019-04-19 | 1 | -0/+12 | |
| | | ||||||
| * | cargo watch start and stop commands | Bernardo | 2019-04-19 | 5 | -55/+100 | |
| | | ||||||
| * | Prettier | Roberto Vidal | 2019-04-16 | 1 | -2/+1 | |
| | | ||||||
| * | Fixes unrelated process termination quirk | Roberto Vidal | 2019-04-16 | 1 | -0/+0 | |
| | | ||||||
| * | Adds "restart server" command | Roberto Vidal | 2019-04-16 | 2 | -1/+20 | |
| | | ||||||
| * | Sends cwd info for runnables and code lenses | Roberto Vidal | 2019-04-14 | 1 | -1/+2 | |
| | | ||||||
| * | Adds support for multiple editor workspaces on initialization | Roberto Vidal | 2019-04-14 | 1 | -7/+0 | |
| | | | | | This is a quick, partial fix for #1104 | |||||
| * | Fix eslint errors | Emil Lauridsen | 2019-04-03 | 1 | -1/+1 | |
| | | ||||||
| * | Add extra double quotes only on Windows. | Emil Lauridsen | 2019-04-03 | 1 | -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 Lauridsen | 2019-04-03 | 1 | -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 refactoring | Edwin Cheng | 2019-04-02 | 2 | -44/+78 | |
| | | ||||||
| * | Fix prettier error | Edwin Cheng | 2019-04-02 | 1 | -1/+1 | |
| | | ||||||
| * | Add terminate process implemntation note | Edwin Cheng | 2019-04-02 | 1 | -0/+7 | |
| | | ||||||
| * | Add Cargo.toml file check before cargo watch start | Edwin Cheng | 2019-04-02 | 1 | -0/+22 | |
| | | ||||||
| * | Add cargo-watch.check-arguments | Edwin Cheng | 2019-04-02 | 5 | -74/+137 | |
| | | ||||||
| * | Add config for cargo-watch trace | Edwin Cheng | 2019-04-02 | 4 | -15/+66 | |
| | | ||||||
| * | Add proper process teminate method | Edwin Cheng | 2019-04-02 | 6 | -10/+116 | |
| | | ||||||
| * | Fix prettier error | Edwin Cheng | 2019-04-02 | 4 | -22/+31 | |
| | | ||||||
| * | Fixed tslint error | Edwin Cheng | 2019-04-02 | 1 | -1/+1 | |
| | | ||||||
| * | Fix tslint error | Edwin Cheng | 2019-04-02 | 2 | -63/+65 | |
| | | ||||||
| * | Improve cargo-watch usage | Edwin Cheng | 2019-04-02 | 4 | -36/+177 | |
| | | ||||||
| * | Don't execute cargo watch when popup is dismissed | pcpthm | 2019-03-22 | 1 | -2/+2 | |
| | | ||||||
| * | Change enableCargoWatchOnStartup to have three states | Ville Penttinen | 2019-03-21 | 3 | -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 CI | Igor Matuszewski | 2019-03-18 | 1 | -9/+7 | |
| | | ||||||
| * | Guard auto cargo watch behind a config option | Igor Matuszewski | 2019-03-18 | 3 | -0/+17 | |
| | | ||||||
| * | Separate out the interactive cargo watch procedure | Igor Matuszewski | 2019-03-18 | 2 | -64/+70 | |
| | | ||||||
| * | Reformat using Prettier | Igor Matuszewski | 2019-03-18 | 2 | -17/+35 | |
| | | ||||||
| * | Remove unused imports | Igor Matuszewski | 2019-03-18 | 1 | -2/+1 | |
| | | ||||||
| * | Prefer installing `cargo-watch` via Task API | Igor Matuszewski | 2019-03-18 | 1 | -23/+14 | |
| | | | | | This gives us much more fine-grained stdout buffering and ANSI terminal colors. | |||||
| * | Respect the user-provided label when creating task | Igor Matuszewski | 2019-03-18 | 1 | -1/+1 | |
| | | ||||||
| * | Ask the user to install and start cargo watch | Igor Matuszewski | 2019-03-18 | 1 | -5/+61 | |
| | | ||||||
| * | Define a cargo watch task | Igor Matuszewski | 2019-03-18 | 1 | -1/+21 | |
| | | ||||||
| * | Remove redundant Runnable.range | Igor Matuszewski | 2019-03-18 | 1 | -1/+0 | |
| | | ||||||
| * | activate extension if Cargo.toml is present | Aleksey Kladov | 2019-03-13 | 1 | -1/+2 | |
| | | ||||||
 |
index : rust-analyzer | |
| [FORK] modified to work on wasm targets |
| aboutsummaryrefslogtreecommitdiff |