Returning error details instead only the error message in group.errors

[delixfe]

I work currently in a project where we have the requirement to show all errors in a list.

The errors can come from several tabs. A click on a link (blue) opens the correct tab and focuses the corresponding input field.

knockout.validation currently does not support such scenarios because group only returns error messages as strings.

That pull requests extents knockout.validation.group to return error detail objects instead only strings.

That is enabled with a new configuration option: enableErrorDetails
If it is set to true then validateables will be extended with an property errorDetails which contains the following values:

if(configuration.enableErrorDetails) {
    // holds detailed error information  
    observable.errorDetails = {
        rule: ko.observable(null),
        params: ko.observable(null),
        observable: observable,
        message: ko.observable(null)
     };           
}

Setting enableErrorDetails to true also lets group.errors return an observable array of errorDetails objects instead of strings. That gives the power to build more complex error lists.

The changeable properties of errorDetails are knockout observables. That solves the problem that the errors of the result of validation.group are not correctly updated if only the type of the error changes, e.g. going from a required to a minimum length error (as described in #218).

[dealproc]

cool. hoping that script# and typescript get updates to reflect this as well.

hoping as changes like this are done, those that are doing the change are thumbing out how you'd do it from JavaScript generators, as well as virgin JavaScript.

will you be providing examples for the scenarios this was built for @delixfe ?? especially how you bound to the right tab set?

[kiaplayer]

@delixfe: Thanks. But why so many commits? Please, use "git rebase" or "git commit --amend" next time.

[dsample]

Any movement on this? We've taken this patch into our project to see how it works and it's much better than the basic string array, although even with the field's observable available to us it's still hard to find the field name.

We're trying to do exactly the same thing as @delixfe has created the patch for, posting the validation errors at the top of the page to guide the user. @delixfe do you have some example code for your scenario of how you get the field name and shortened error text?