Sometimes it's nice to be able validate field differently depending on the input itself.
allows the validators object and validator options to be a function that should return the constraints/options: Validates the attributes object against the constraints.
The project can be found on Git Hub where you can also find our issue tracker.
There is also a Travis project used for testing, a Coveralls project used to code coverage as well as the annotated source.
Besides accepting all options as the non async validation function it also accepts two additional options; clean Attributes which, unless before resolving the promise and wrap Errors which can be a function or constructor that will be called with the errors, options, attributes and constraints if an error occurs.
This allows you to define a better way of catching validation errors.
You can use the async validate function even if no validations are async, it still returns a promise.
You can not, however, use the regular function with async validations.The validation constraints can be declared in JSON and shared between clients and the server. One thing that is a bit unorthodox is that most validators will consider undefined values (,) valid values.So for example adding a constraint of at least 6 characters will be like saying If the attribute is given it must be at least 6 characters.Any A type promise can be used, just override function success(attributes) function error(errors) var constraints = ; var attributes = ; // Will call the success function and log validate.async(attributes, constraints).then(success, error); // Will call the error function validate.async(, constraints).then(success, error); function Validation Errors(errors, options, attributes, constraints) Validation Errors.prototype = new Error(); // This isn't supported by the ES6 promises validate.async(, constraints, ) .then(success) .catch(Validation Errors, function(error) ) .catch(function(error) ); // Supporting another promise implementation (RSVP in this case) validate. Promise; Sometimes you only want to validate a single value against some constraints and using the normal validate function is quite verbose so there is a shorthand for this.It does little more than proxying the call do the main validation function but with the value wrapped in an object and the options full Messages and format set to also has limited support for nested objects (objects within objects) using the dot notation.One core value of this library is that nothing should be private or inaccessable.