-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Qute can't find all fields defined on parent interfaces with strict rendering enabled #19564
Comments
/cc @mkouba |
I noticed this especially after trying the |
Thanks for reporting! The problem is that we only consider interface default methods. I'm not sure why exactly. I'll take a deeper look tomorrow. |
Hm, I didn't find a reason why only default methods, so here's the PR: #19722 |
Thanks a lot! Already had a look at the processor the other day myself, but wasn't sure if and what to change. Any chance we could still include this for the 2.2 release of next week? |
I've marked the PR with the |
Cool 😄 |
- resolves quarkusio#19564 (cherry picked from commit 55288bf)
Describe the bug
Looks like Qute can't find certain fields when you use a nested class hierarchy.
For example, in our project we extensively use Immutables for our domain objects. And we use wrappers around primitives, see https://immutables.github.io/immutable.html#wrapper-types
When we use this in combination with checked templates and strict rendering it does not work and Qute complains about incorrect expressions. See the example below:
However when we don't use checked templating or disable the strict rendering it does work as expected.
If I provide an extra method on
Wrapper.class
it does work again:Expected behavior
No response
Actual behavior
No response
How to Reproduce?
Provided a reproducer here https://github.com/wjglerum/quarkus-qute-strict
Output of
uname -a
orver
Output of
java -version
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.1.2.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)Additional information
No response
The text was updated successfully, but these errors were encountered: