Skip to content
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

Client never sets partialResultToken and only sets workDoneToken during initialize #528

Open
david-driscoll opened this issue Oct 13, 2019 · 5 comments
Labels
depends on VS Code feature-request Request for new features or functionality
Milestone

Comments

@david-driscoll
Copy link

Currently workDoneToken only gets set by the client during initialize. And no place is the partialResultToken assigned as far as I can tell.

I'm not sure if it's implemented or not (leaning on not).

  • Are these waiting for APIs on the vscode side to be completed before being plumbed through everything?
  • How would these be implemented appropriately (to help by making a PR)?
@dbaeumer
Copy link
Member

@david-driscoll VS Code has currently no support for work done and partial result progress. Although they are in the spec (mainly because other clients were asking for them) it will take a while until VS Code will support them.

Is there a special feature you want to see supported first?

@dbaeumer dbaeumer added this to the Backlog milestone Oct 14, 2019
@david-driscoll
Copy link
Author

Nope! Usually these things land in VSCode around the same time as they do in the spec, as I was implementing them in the C# LSP library I wanted to validate that they were working as expected.

I was just want to make sure I wasn't missing something. 😄 Thanks!

@heejaechang
Copy link
Contributor

@dbaeumer if we need to ping vscode people to add this new feature (incrementally update UI/results for Workspace Symbols or Find All References) who should we talk to?

@dbaeumer
Copy link
Member

dbaeumer commented Sep 1, 2020

@heejaechang you need to open an issue against VS Code (see also microsoft/vscode#20010)

@heejaechang
Copy link
Contributor

opened microsoft/vscode#105870

perrinjerome added a commit to perrinjerome/pygls that referenced this issue Jul 10, 2022
It seems there was a confusing with workDoneProgressParams and
workDoneProgressOptions.

[workDoneProgressParams](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workDoneProgressParams)
is the type used for the token in methods and notifications, it is the
token itself, so it has type str | int. This type is correct, this was
to explain context.

[workDoneProgressOptions](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workDoneProgressOptions)
is the type used for registration, it is used to indicate if work done
progress are supported, so it is a boolean. This type was wrong.

It seems as of today vscode does include workDoneProgress in requests:
 - microsoft/vscode-languageserver-node#528 (comment)
 - microsoft/vscode#105870
perrinjerome added a commit to perrinjerome/pygls that referenced this issue Jul 10, 2022
It seems there was a confusing with WorkDoneProgressParams and
WorkDoneProgressOptions.

[WorkDoneProgressParams](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workDoneProgressParams)
is the type used for the token in methods and notifications, it is the
token itself, so it has type str | int. This type is correct, this was
to explain context.

[WorkDoneProgressOptions](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workDoneProgressOptions)
is the type used for registration, it is used to indicate if work done
progress are supported, so it is a boolean. This type was wrong.

It seems as of today vscode does include workDoneProgress in requests:
 - microsoft/vscode-languageserver-node#528 (comment)
 - microsoft/vscode#105870
@dbaeumer dbaeumer added feature-request Request for new features or functionality and removed feature request labels Nov 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
depends on VS Code feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

3 participants