aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_syntax/tests/data/parser/inline
diff options
context:
space:
mode:
authorbors[bot] <bors[bot]@users.noreply.github.com>2019-04-02 11:10:26 +0100
committerbors[bot] <bors[bot]@users.noreply.github.com>2019-04-02 11:10:26 +0100
commitbb3b159fb7d377f667732ade715cbe019da84d71 (patch)
tree2cfb500a2eec37f1689ec9448babbbfedc28fba0 /crates/ra_syntax/tests/data/parser/inline
parentb0d244719323d68905986857844f56d1fa38cac4 (diff)
parentb60e2f779b28f654dbd5a2657c668de8452933c6 (diff)
Merge #1079
1079: Improve cargo-watch usage in vscode plugin r=matklad a=edwin0cheng *This PR try to improve current cargo-watch usage in VSCode :* 1. Add Multi-lines error support : ![multilines-error](https://i.imgur.com/gbLEwMG.gif) 2. Add cargo-watch status animation : ![cargo-watch-status](https://i.imgur.com/GbHwzjj.gif) *Implementation Details* * Current VSCode `ProblemMatcher` still do not support multiple line parsing. * However we can, spawn a cargo watch process instead of using vscode.Task to allow more control. * Use `cargo-check --message-format json` to get json format of compiler-message. * Use `vscode.DiagnosticCollection` to manage the problems directly, which allow multiple lines diagnostic. However, * VSCode use non mono-space font for problems, at this moment i cannot find a good solution about it. * I am not so good in typescript, please let me know if anything is bad in this PR. Co-authored-by: Edwin Cheng <[email protected]> Co-authored-by: Edwin Cheng <[email protected]>
Diffstat (limited to 'crates/ra_syntax/tests/data/parser/inline')
0 files changed, 0 insertions, 0 deletions