redhat-developer / redhat-developer/quarkus-ls
Classes annotated with user provided `@CheckedTemplate` annotation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 50
- Forks
- 18
- Avg merge
- 22h 11m
- Merged PRs (30d)
- 3
Description
To reproduce the issue: create an annotation class org.acme.CheckedTemplate:
package org.acme;
public @interface CheckedTemplate {
}
Then, annotate a class with it as if it were the actual @CheckedTemplate. You will get the code lenses that link to the template files, as if io.quarkus.qute.CheckedTemplate were being used.
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
Reproduce the issue with the org.acme.CheckedTemplate annotation and compare it with io.quarkus.qute.CheckedTemplate. Trace the language server's code-lens handling for annotated classes, then verify that lenses are produced only for the actual Quarkus annotation and not for user-provided annotations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100