eclipse-lsp4e / eclipse-lsp4e/lsp4e
Implement LSP specified languageIds
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 85
- Forks
- 69
- Avg merge
- 8h 33m
- Merged PRs (30d)
- 6
Description
The Language Server Protocol does specify some languageIds to use according to the language: https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocumentItem
Currently, LSP4E requires that those languageIds are set in the contentTypeMapping, but in case they aren't, LSP4E should fail-back to a dummy implementation implementing the spec (ie mapping fileExtension->languageId as described).
Contributor guide
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 tracing how LSP4E reads contentTypeMapping and assigns languageIds, then compare that behavior with the LSP 3.17 TextDocumentItem specification linked in the issue. Done means configurations without explicit mappings use the specified file-extension-to-languageId fallback instead of requiring every languageId in contentTypeMapping.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100