-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manual validation mode #7902
Comments
LoginForm is a potential candidate to use this feature. Triggering validation only on submit could help avoid content shifts currently caused by automatic validation, see #7894 (comment) |
This might also be a proper solution for Flow components to disable client-side validation. Currently we override the |
Prototype branch with Note: if we decide to also use this in Flow like suggested above, we might also need to replace |
Describe your motivation
Automatic constraint validation on every field change isn't always suitable. Consider these cases:
Describe the solution you'd like
For such cases, a manual validation mode (similar to that in Flow components) would be beneficial. It would disable the automatic validation but leave the option to trigger it programmatically by calling the
validate()
method, or alternatively, control the invalid state completely manually.Here is how the API could look like:
The text was updated successfully, but these errors were encountered: