microsoft / microsoft/language-server-protocol
A way for a LS to declare its project association cardinality
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
With the XML language server and many others, a same LS can be used for any matching file on filesystem and no new instance is required.
At the moment, the only specified concept regarding multiplicity, association and spawning language servers is through workspaceFolders ( #281 , #289 ). But for the LS that have no interest at all in workspaceFolders, it seems strange to declare this compatibility.
Instead, the spec could have as a ServerCapability a flag describing whether it can serve arbitrary files, ignoring the rootUri and workspaceFolders.
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
Start by reading the language-server protocol sections covering workspaceFolders, rootUri, spawning, and ServerCapability, along with issues #281 and #289. Define how a capability for arbitrary-file service would fit the specification and what compatibility behavior it should establish.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100