redhat-developer / redhat-developer/quarkus-ls
Improve performance for Codelens in Java
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 50
- Forks
- 18
- Avg merge
- 22h 11m
- Merged PRs (30d)
- 3
Description
When Qutetemplate doesn't exists it shows Create codelens. The computation of this codelens takes some times because it must resolve the JDT type of the method.
Improve this computation outside of the process of report codelens (use resolve codelens, or resolve the method parameters java type only whencodelens is clicked)
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 the Java Codelens reporting path for the Create codelens shown when a Qute template does not exist. Measure where resolving the JDT method type occurs, then defer that resolution until the codelens is resolved or clicked. Done means reporting no longer performs the expensive type resolution while preserving the Create codelens behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100