-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Progress reporting should respect client capabilities #4384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
We added support for server-initiated progress reporting in 0.10.1. However, it looks like rust-analyzer doesn't request The general flow of messages should look like this: server -> editor request The |
I have been testing this a bit, and when setting the project folder properly, it seems to initiate the progress correctly:
On the other hand, when opening a single file that doesn't belong to a project (
|
Looks good when there are workspaceFolders. I do see this lonely progress notification:
|
4403: Check client capabilities before sending progress notifications r=kjeremy a=kjeremy Fixes #4384 Co-authored-by: Jeremy Kolb <[email protected]>
I wonder if every progress should initiate the |
See https://microsoft.github.io/language-server-protocol/specifications/specification-current/#signalingWorkDoneProgressReporting, CC #144.
This affects Sublime, for example.
The text was updated successfully, but these errors were encountered: