redhat-developer / redhat-developer/quarkus-ls
Only show one "add to existing template extensions class" code action
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 50
- Forks
- 18
- Avg merge
- 22h 11m
- Merged PRs (30d)
- 3
Description
As of now, we show one "add to existing template extensions class" code action for each class that's annotated with @TemplateExtension. As per comments from Fred, it would be less cluttered if we only showed one of these code actions. It's not just a matter of reverting https://github.com/redhat-developer/quarkus-ls/commit/635bedf3bc738108f21c228af27dd6d8d22fd8b8, since the functionality of knowing which class the code will be added to is important.
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 reviewing commit 635bedf3bc738108f21c228af27dd6d8d22fd8b8 and the code-action generation for classes annotated with @TemplateExtension. Determine how one action can represent the available target classes while preserving which class receives the added code. Done means only one such code action is shown without losing target-class information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100