microsoft / microsoft/language-server-protocol
Semantic regions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13k
- Forks
- 1k
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 10
Description
Languages often have sections/regions that have different meaning.
It would be great if the LSP server could inform the client about this regions, so they could handle them differently. Specifically, it is often a good idea to change the background of these regions to convey the information in a fast and easy way.
For example, in C++, the following regions have some meaning for the programmer:
- public/private/protected inside a class/struct.
- multiline comment. (already covered by the tokens, but could also be covered as a region)
- anonymous namespaces
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
Read issue #1192 and the existing Language Server Protocol definitions first; the payload does not name an implementation file or test. Determine how a protocol extension for semantic regions would be specified and validated, including the C++ examples, and consider the proposal complete only when its scope and client-server behavior are defined.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100