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 we have a number of components (Iban, License Plate, Postcode) where the schema defaults to validateOn: blur, while other components default to validateOn: change (the Formio default).
This leads to inconsistent behaviour. Other than that, from Taiga issue 273 it's clear that (some) clients expect the validateOn: change behaviour, while we had a tendency to prefer on blur.
Formio allows form designers to specify the validation event trigger, so we should expose that configuration and remove the default overrides. This allows every client/tenant to configure the triggers per component as they see fit.
Tasks
Expose "validate on" configuration in form designer for all components
Remove custom default overrides for validateOn
in SDK
in backend
The text was updated successfully, but these errors were encountered:
Currently we have a number of components (Iban, License Plate, Postcode) where the schema defaults to
validateOn: blur
, while other components default tovalidateOn: change
(the Formio default).This leads to inconsistent behaviour. Other than that, from Taiga issue 273 it's clear that (some) clients expect the
validateOn: change
behaviour, while we had a tendency to prefer on blur.Formio allows form designers to specify the validation event trigger, so we should expose that configuration and remove the default overrides. This allows every client/tenant to configure the triggers per component as they see fit.
Tasks
validateOn
The text was updated successfully, but these errors were encountered: