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
Attempting to use a custom validation to allow one field or another (but not both) is quite difficult right now because the custom validation only executes if the field has a value.
I propose changing this behaviour to always execute custom validation, even if the field is not filled.
This would be a breaking change if anyone is currently depending on the behaviour as is now. An alternative is to add a different kind of validator that will run all the time, even on empty fields so there is a way to have both behaviour.
I think having the custom validator always run, even when a field is not filled in is the most powerful approach as this way the user can simply return true from their custom validator if the value is empty.
The text was updated successfully, but these errors were encountered:
Attempting to use a custom validation to allow one field or another (but not both) is quite difficult right now because the custom validation only executes if the field has a value.
I propose changing this behaviour to always execute custom validation, even if the field is not filled.
This would be a breaking change if anyone is currently depending on the behaviour as is now. An alternative is to add a different kind of validator that will run all the time, even on empty fields so there is a way to have both behaviour.
I think having the custom validator always run, even when a field is not filled in is the most powerful approach as this way the user can simply return true from their custom validator if the value is empty.
The text was updated successfully, but these errors were encountered: