You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the value resolvers that are generated based on type-safe validation findings are optimized, i.e. only fields/methods used in templates are considered. All other members are ignored. However, this does not play well with included templates and user tags. For example, if there is a template that is validated (because it either has a param declaration or is used from a type-safe template) like this:
Description
Currently, the value resolvers that are generated based on type-safe validation findings are optimized, i.e. only fields/methods used in templates are considered. All other members are ignored. However, this does not play well with included templates and user tags. For example, if there is a template that is validated (because it either has a param declaration or is used from a type-safe template) like this:
and in the
foo
template there is:Then only
item.name
is considered anditem.price
is ignored, unless the included template also declares the param declaration, e.g.This may cause problems when generating native images.
Implementation ideas
We should probably introduce a new config property
quarkus.qute.optimize-value-resolvers
and disable the optimization by default.The text was updated successfully, but these errors were encountered: