Qute Generated ValueResolver for interface default methods #43489
Comments
|
/cc @mkouba (qute) |
mkouba
added a commit
to mkouba/quarkus
that referenced
this issue
Sep 30, 2024
- fixes quarkusio#43489 - previously, interface default methods were only considered if a ValueResolver was generated for an interface
mkouba
added a commit
to mkouba/quarkus
that referenced
this issue
Sep 30, 2024
- fixes quarkusio#43489 - consider default methods in class hierarchy; previously, interface default methods were only considered if a ValueResolver was generated for an interface - also consider inherited fields in a class hierarchy
mkouba
added a commit
to mkouba/quarkus
that referenced
this issue
Sep 30, 2024
- fixes quarkusio#43489 - consider default methods in class hierarchy; previously, interface default methods were only considered if a ValueResolver was generated for an interface - also consider inherited fields in a class hierarchy
mskacelik
pushed a commit
to mskacelik/quarkus
that referenced
this issue
Oct 2, 2024
- fixes quarkusio#43489 - consider default methods in class hierarchy; previously, interface default methods were only considered if a ValueResolver was generated for an interface - also consider inherited fields in a class hierarchy
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Nov 13, 2024
- fixes quarkusio#43489 - consider default methods in class hierarchy; previously, interface default methods were only considered if a ValueResolver was generated for an interface - also consider inherited fields in a class hierarchy (cherry picked from commit bc206a1)
bschuhmann
pushed a commit
to bschuhmann/quarkus
that referenced
this issue
Nov 16, 2024
- fixes quarkusio#43489 - consider default methods in class hierarchy; previously, interface default methods were only considered if a ValueResolver was generated for an interface - also consider inherited fields in a class hierarchy
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Currently it uses the reflection value resolver
Expected behavior
It should generate a valueresolver
The text was updated successfully, but these errors were encountered: