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
{{ message }}
This repository has been archived by the owner on Sep 8, 2020. It is now read-only.
When I my validation expression returns false, the invalid value is bound to the model, anyway. This isn't how any of the pre-canned or custom validators work. Why does it behave this way?
The text was updated successfully, but these errors were encountered:
I also noticed this. If you use ui-validate-async, the model is updated prior to the validation completing, so feasibly if the validation requires a httprequest, someone can fill in a valid value, then change it to an invalid one, and quickly hit the submit button before the validation completes.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When I my validation expression returns false, the invalid value is bound to the model, anyway. This isn't how any of the pre-canned or custom validators work. Why does it behave this way?
The text was updated successfully, but these errors were encountered: