I currently have a working grid with inline editing. I need validation that needs to be done on the server side. Using clientside unobtrusive validation is a perfect user experience, but server side modelstate errors aren't so intuitive.
Currently, lets say you leave a required field empty and it is validated server side. The grid will change back to read-only appearing that is was a valid save, but the error handle gets called for you to display the error how you like. Then if you edit the row again and cancel, the original value comes back.
I'd like to see better default handling of validation errors. Currently, the json result comming back with the update has a field name and errors. We should at minimum add an error class to the row indicating it wasn't saved, and maybe even the td for the given field.
If the error handler had a reference to the tr that handled the error, I can manually add my own error class, but that currently isn't possible, is it?
Currently, lets say you leave a required field empty and it is validated server side. The grid will change back to read-only appearing that is was a valid save, but the error handle gets called for you to display the error how you like. Then if you edit the row again and cancel, the original value comes back.
I'd like to see better default handling of validation errors. Currently, the json result comming back with the update has a field name and errors. We should at minimum add an error class to the row indicating it wasn't saved, and maybe even the td for the given field.
If the error handler had a reference to the tr that handled the error, I can manually add my own error class, but that currently isn't possible, is it?