microsoft / microsoft/vscode-languageserver-node
Client never sets `partialResultToken` and only sets `workDoneToken` during `initialize`
Open
Nobody has claimed this yet.
depends on VS Code
feature-request
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 404
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 14
Description
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)?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Start by tracing where the client sets workDoneToken during initialize and checking whether partialResultToken is assigned elsewhere. Review the VS Code-side APIs mentioned in the issue; done means the required token support is clearly scoped and covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100