Build better business applications, faster. No more juggling REST endpoints or deciphering GraphQL queries. Hilla seamlessly connects Spring Boot and React to accelerate application development.
It seems that trivial self-defined pattern meta-annotations are not brought to the client side by Vaadin Fusion.
Minimal reproducible example / Actual behavior
Please see an example of such a validation.
This validation works correctly on the server side, but not on the client side. We use such a self-defined annotation so we don't have to duplicate the pattern in multiple locations.
Expected behavior
It would be good if 'meta-annotation'-based validation patterns can be brought to the client side, since the field input can be fully validated there.
Description of the bug / feature
It seems that trivial self-defined pattern meta-annotations are not brought to the client side by Vaadin Fusion.
Minimal reproducible example / Actual behavior
Please see an example of such a validation. This validation works correctly on the server side, but not on the client side. We use such a self-defined annotation so we don't have to duplicate the pattern in multiple locations.
Expected behavior
It would be good if 'meta-annotation'-based validation patterns can be brought to the client side, since the field input can be fully validated there.
Versions:
Thanks...!