-
-
Notifications
You must be signed in to change notification settings - Fork 128
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
API to add/remove errors #261
Comments
I agree that it is nicer if server side issues can highlight the relevant input field. A simple extension to the validation controller would be ideal. |
We're definitely going to add this. It supports a very common validation pattern where simple rules are validated synchronously, data is submitted to the server and if the server returns errors, they can be rendered in the UI- basic async validation. |
My question with this is how to know the When the Add button is clicked how do I validate just Date of Loss, Loss Amount, and Reason of Loss? If I'm able to that and get errors then how would I use |
How will the target be determined? The How do I validate a single item in my detail grid?
|
It would be great to have such a feature. I was looking for ways to do that and landed here. I would suggest that |
closing- this was added in friday's release. |
It would be nice to have some kind of
addError()
andremoveError()
API on the validation controller.Use cases:
For example, your model contains a
contact: Person
property and you use a custom control to pick aPerson
class by its name. Imagine the user types an incorrect name. Short of consideringundefined
an error signal, this is hard to detect on the model alone.For example, you tried to save but the server returned a unique key violation on the name of your entity (note: async validation can't cover this use case in the face of concurrency... you may add async valdiation or not, but you should always be ready to handle failure at commit time.) It would be nice to be able to map this error back to the name field in the UI.
The text was updated successfully, but these errors were encountered: