redhat-developer / redhat-developer/lsp4ij
Make LSP-based EP implementations `DumbAware` as much as (safely) possible
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 344
- Forks
- 113
- Avg merge
- 5h 22m
- Merged PRs (30d)
- 15
Description
It occurred to me that many/most of the EP implementations in LSP4IJ could likely be DumbAware, i.e., allowed to run while the IDE is indexing. I'm sure there are some that need stable indexes either directly or transitively, but most of them are just delegating to a language server to get information, and they should be able to do that even during indexing. I know there is some caution around not starting language servers during indexing, and that would need to be preserved/respected, but the most of these features that can be made DumbAware, the more respective those features will be.
Something to consider...
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 inventorying the LSP4IJ extension-point implementations and checking which ones depend directly or transitively on stable indexes. Preserve the restriction against starting language servers during indexing. Done means each implementation that is safely usable while indexing is made DumbAware, with unsafe cases left unchanged and coverage or validation added where the project provides it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100