redhat-developer / redhat-developer/quarkus-ls
Validation for duplicate Qute TemplateExtension
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 50
- Forks
- 18
- Avg merge
- 22h 11m
- Merged PRs (30d)
- 3
Description
Given those 2 classes which defines the same foo TemplateExtension:
package util;
import io.quarkus.qute.TemplateExtension;
public class CLassA {
@TemplateExtension
public static boolean foo() {
return true;
}
}
and
package util;
import io.quarkus.qute.TemplateExtension;
public class CLassB {
@TemplateExtension
public static boolean foo() {
return false;
}
}
We should study the behavior of the Qute (perhapsit reports some error when the Qute application is compiled). According the behavior we should perhaps reporting error like duplicate foo TemplateEtension.
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 reproducing the two util classes shown in the issue and observe whether Qute reports the duplicate foo TemplateExtension during application compilation. Then locate the quarkus-ls validation path for Qute TemplateExtension declarations. Done means duplicate extensions are reported with a clear diagnostic, or the observed Qute behavior is documented if no validation is appropriate.
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