redhat-developer / redhat-developer/lsp4ij
Introduce LanguageServerWrapper#getServerCapabilitiesAsync
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 344
- Forks
- 113
- Avg merge
- 5h 22m
- Merged PRs (30d)
- 15
Description
I created the issue because I wanted to do that since long time (because code was copied/pasted from LSP4E and I had created an issue at https://github.com/eclipse/lsp4e/issues/628)
and LSP4E start to fix that https://github.com/eclipse/lsp4e/pull/1098
I create the issue to remember that it should be good to use getServerCapabilitiesAsync
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 LanguageServerWrapper#getServerCapabilitiesAsync entry point and compare the copied implementation with LSP4E issue #628 and pull request #1098. Trace the existing server-capabilities handling and its callers; done means the wrapper exposes and uses the asynchronous capability lookup as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100