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
As illustrated in #4196, field components don't trigger validation consistently on constraint property change.
Let's align their behavior in the following way:
Trigger validation on constraint property changes if the field has a value (because the value can possibly be invalidated by the new constraints configuration)
Trigger validation during initialization if at least one constraint is defined and the field has a value (providing an initial value that doesn't match constraints sounds more like an edge case and rather an app business logic error, but if this has happened by any chance, it is better to provide immediate feedback for the user to be able to correct the value)
vursen
changed the title
Always trigger validation on constraint properties' change
Always trigger validation on constraint property changes
Aug 19, 2022
vursen
changed the title
Always trigger validation on constraint property changes
trigger validation on constraint property changes if the field has a value
Aug 19, 2022
vursen
changed the title
trigger validation on constraint property changes if the field has a value
Validate on constraint property changes if the field has a value
Aug 19, 2022
As illustrated in #4196, field components don't trigger validation consistently on constraint property change.
Let's align their behavior in the following way:
A related ticket for Flow components: vaadin/flow-components#2370
The text was updated successfully, but these errors were encountered: