diff options
| author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2019-12-29 12:57:24 +0000 |
|---|---|---|
| committer | GitHub <[email protected]> | 2019-12-29 12:57:24 +0000 |
| commit | dc48f89581843248660ceb755bb20469ab6ac0c9 (patch) | |
| tree | 05a7e47d1c68c250025be1ce6492f56c15353749 /crates/ra_hir_ty | |
| parent | cdcb3d3833d3d5b37b2cd4dac91a6e9366f20aea (diff) | |
| parent | 899dbebd02b41b12d89c9f485e85208b39b81932 (diff) | |
Merge #2668
2668: In-server cargo check watching r=matklad a=kiljacken
Opening a draft now so people can follow the progress, and comment if they spot something stupid.
Things that need doing:
- [x] Running cargo check on save
- [x] Pipe through configuration options from client
- [x] Tests for parsing behavior
- [x] Remove existing cargo watch support from VSCode extension
- [x] Progress notification in VSCode extension using LSP 3.15 `$/progress` notification
- [ ] ~~Rework ra-ide diagnostics to support secondary messages~~
- [ ] ~~Make cargo-check watcher use ra-ide diagnostics~~
~~I'd love some input on whether to try to keep the status bar progress thingy for VSCode? It will require some plumbing, and maintaining yet another rust-analyzer specific LSP notification, which I'm not sure we want to.~~
Fixes #1894
Co-authored-by: Emil Lauridsen <[email protected]>
Diffstat (limited to 'crates/ra_hir_ty')
0 files changed, 0 insertions, 0 deletions