redhat-developer / redhat-developer/quarkus-ls
Generated template extensions class should not be in default package
Open
Nobody has claimed this yet.
code action
enhancement
qute
- Dominant language
- Java
- Stars
- 50
- Forks
- 18
- Avg merge
- 22h 11m
- Merged PRs (30d)
- 3
Description
As of now, when you generate a template extension in a new template extension class for a missing member in a qute template, the generated class is always put in the default package. It would be nice to put it somewhere other than the default package.
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
No file or test is named. Start by tracing the Qute template-extension generation path for missing members and how it selects the generated class package. Done means generated template extension classes are placed somewhere other than the default package, with coverage for the resulting package selection.
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
- Mostly clear
- Newbie friendliness
- 35/100