microsoft / microsoft/language-server-protocol
Should the client announce the schema it supports in URI's
Open
Nobody has claimed this yet.
document
feature-request
initialization
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
Server are allowed to send URI back which might not have a file or other well known schema. These URI's might not be handled correctly by the client.
Should the client announce it's handled schemas to the server and inform the server about any schema handler changes?
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
No files, tests, or entry points are identified in the issue. Start by reviewing the language server protocol's URI handling and client/server capability negotiation; done would require a decided protocol design for supported schemas and handler changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100