eclipse-lsp4e / eclipse-lsp4e/lsp4e
a LanguageServers.forUri(...) method
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 85
- Forks
- 69
- Avg merge
- 8h 33m
- Merged PRs (30d)
- 6
Description
As I'm integrating support for some commands in a specific language server, using the LanguageServers API, I realize that we can often not have the document at hand, nor even need it to use a document or a project. A URI is often enough, so a LanguageServers.forURI(uri) method would be useful.
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 with the LanguageServers API and inspect its existing document- or project-based lookup methods. Determine where URI-based lookup belongs and add coverage for resolving a language server when only a URI is available; done means callers can use LanguageServers.forURI(uri) without a document or project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100