diff options
| author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2020-03-16 11:48:46 +0000 |
|---|---|---|
| committer | GitHub <[email protected]> | 2020-03-16 11:48:46 +0000 |
| commit | 5bdc249b2c938df3eb2799c5efbdf1aa95d32a17 (patch) | |
| tree | 8f3911d67773d8fc7af55234dfbdd4d0a7ad4f8a /crates/ra_syntax/test_data/parser/fuzz-failures | |
| parent | 2eb1677b12f15a377111e877f6a09e1a1550c8be (diff) | |
| parent | b6dec2eb1f8b84cbf892d43c7d4afc00e747328a (diff) | |
Merge #3587
3587: Use WorkDoneProgress LSP API for initial load r=matklad a=slyngbaek
Addresses #3283
Rather than using custom UI for showing the loaded state. Rely
on the WorkDoneProgress API in 3.15.0
https://microsoft.github.io/language-server-protocol/specification#workDoneProgress.
No client-side work was necessary. The UI is not exactly what is
described in the issue but afaict that's how VS Code implements the LSP
API.
- The WorkDoneProgressEnd does not appear to display its message
contents (controlled by vscode)
Co-authored-by: Steffen Lyngbaek <[email protected]>
Diffstat (limited to 'crates/ra_syntax/test_data/parser/fuzz-failures')
0 files changed, 0 insertions, 0 deletions