microsoft / microsoft/language-server-protocol
`workspace.workspaceFolders` client capability missing dynamic registration support
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
The protocol currently specifies that the workspace.workspaceFolders client capability is simply a boolean, but then it isn't clear how a server can tell whether an editor supports dynamic registration for the workspace/didChangeWorkspaceFolders notification.
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
Review the protocol definitions for the workspace.workspaceFolders client capability and the workspace/didChangeWorkspaceFolders notification. Determine how the specification should express support for dynamic registration, then update the relevant protocol definition and confirm the resulting capability semantics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100