microsoft / microsoft/language-server-protocol
communicating file encoding
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
Some programming languages use magic comments at the beginning to specify the encoding of the file. The server and client need to agree on the encoding, so that positions and ranges match. Should the protocol sync this information? Or do we rely on the client and server implementations doing the right thing?
VScode doesn't have support for magic comments yet (created https://github.com/Microsoft/vscode/issues/32764).
https://github.com/Microsoft/language-server-protocol/issues/96#issuecomment-257299369 mentions something about this, but I can't find any follow-up.
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 reviewing the referenced language-server-protocol issue comment and the linked VSCode issue #32764. Determine whether encoding synchronization belongs in the protocol or in client and server implementations. Done means the issue has a resolved direction for handling magic-comment encodings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100