-
Notifications
You must be signed in to change notification settings - Fork 169
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
feat: allow custom constraint validation errors #1023
feat: allow custom constraint validation errors #1023
Commits on Aug 8, 2024
-
feat(input): allow custom constraint validation errors
This feature provides a new way to override the browser's default constraint validation messages, making `validationMessage` unnecessary.
Configuration menu - View commit details
-
Copy full SHA for dd221e6 - Browse repository at this point
Copy the full SHA dd221e6View commit details -
feat(input): make overriding browsers' validation messages easier
With this change, rather than having to duplicate the browser's native validation logic when selecting a custom message, the parent component can just react to the validity state that the browser reports.
Configuration menu - View commit details
-
Copy full SHA for 18f55a3 - Browse repository at this point
Copy the full SHA 18f55a3View commit details -
fix(inputs): fix constraint validation for nested controls
For controls nested inside each other, the parent usually component handles constraint validation concerns, so there's no need for the children to also handle validation; in fact, they can cause incorrect changes to the field state if their validation isn't suppressed. The one exception is that the child control which actually owns the "main" input element must forward the `invalid` event to the parent control.
Configuration menu - View commit details
-
Copy full SHA for 570625b - Browse repository at this point
Copy the full SHA 570625bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 7cfd4d1 - Browse repository at this point
Copy the full SHA 7cfd4d1View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0b56f32 - Browse repository at this point
Copy the full SHA 0b56f32View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9bcc478 - Browse repository at this point
Copy the full SHA 9bcc478View commit details -
Configuration menu - View commit details
-
Copy full SHA for e0635f8 - Browse repository at this point
Copy the full SHA e0635f8View commit details -
fix(datetimepicker): solve editing directly not working correctly (or…
…uga-ui#1026) * fix(picker): solve editing directly not working * fix(picker): make locale property reactive * test: update tests
Configuration menu - View commit details
-
Copy full SHA for 05e392e - Browse repository at this point
Copy the full SHA 05e392eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 55e3883 - Browse repository at this point
Copy the full SHA 55e3883View commit details -
Configuration menu - View commit details
-
Copy full SHA for 33f0d7a - Browse repository at this point
Copy the full SHA 33f0d7aView commit details -
feat(input): allow custom constraint validation errors
This feature provides a new way to override the browser's default constraint validation messages, making `validationMessage` unnecessary.
Configuration menu - View commit details
-
Copy full SHA for 4f198b6 - Browse repository at this point
Copy the full SHA 4f198b6View commit details -
feat(input): make overriding browsers' validation messages easier
With this change, rather than having to duplicate the browser's native validation logic when selecting a custom message, the parent component can just react to the validity state that the browser reports.
Configuration menu - View commit details
-
Copy full SHA for 5eb6d3c - Browse repository at this point
Copy the full SHA 5eb6d3cView commit details -
fix(inputs): fix constraint validation for nested controls
For controls nested inside each other, the parent usually component handles constraint validation concerns, so there's no need for the children to also handle validation; in fact, they can cause incorrect changes to the field state if their validation isn't suppressed. The one exception is that the child control which actually owns the "main" input element must forward the `invalid` event to the parent control.
Configuration menu - View commit details
-
Copy full SHA for ae2b8f0 - Browse repository at this point
Copy the full SHA ae2b8f0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 62389eb - Browse repository at this point
Copy the full SHA 62389ebView commit details -
Configuration menu - View commit details
-
Copy full SHA for 5c8fc7f - Browse repository at this point
Copy the full SHA 5c8fc7fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 5b8a761 - Browse repository at this point
Copy the full SHA 5b8a761View commit details -
Configuration menu - View commit details
-
Copy full SHA for 196756e - Browse repository at this point
Copy the full SHA 196756eView commit details -
Merge branch 'custom-constraint-validation' of https://github.com/blm…
…768/oruga into custom-constraint-validation
Configuration menu - View commit details
-
Copy full SHA for 8d36756 - Browse repository at this point
Copy the full SHA 8d36756View commit details