redhat-developer / redhat-developer/quarkus-ls
Add support for #cached sections in Qute templates
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 50
- Forks
- 18
- Avg merge
- 22h 11m
- Merged PRs (30d)
- 3
Description
According to https://quarkus.io/guides/qute-reference#cached-section, if io.quarkus:quarkus-cache is in the classpath, qute templates should automatically be able to use a {#cached} section, with an optional key attribute.
Currently, the #cached section is being shown with an error
@mkouba is this another instance of synthetic bean usage?
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 reading the Qute cached-section reference linked in the issue and reproducing the error for a template using {#cached} with and without its optional key attribute. Then trace the language server's Qute section validation and determine what support is needed when io.quarkus:quarkus-cache is present; done means these sections are no longer reported as errors.
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