I had a need to do some data validation in javascript, and all the libraries I looked at seemed quite opinionated about *what* you were going to validate – i.e. form data – let alone the increase in server-side javascript in the last couple of years. My data wasn’t directly tied to a form, so it didn’t quite seem worthwhile trying to shoe horn my needs into what the libraries expected, and I could also see a need for a validation library that could be adapted for Node.
Enter Validator.js.
Validator’s only dependency is on underscore.js from Document Cloud.
Validator has two usage forms: the first for very quick and simple one-off cases:
// Simple use:
var result
result = Validator.isEmail('not_an_email');
console.log(result); // false
result = Validator.isEmail('joe@example.com');
console.log(result); // true
I found this on its own quite a lot more flexible than most of the form-driven libraries out there. However, I also wanted to be able to create more complex sets of validations to run on a piece of data. For that case, you create an instance of Validator and use it’s add() method:
var result,
myValidator
myValidator = new Validator();
myValidator.add('unique');
myValidator.add('minLength', 6);
result = myValidator.validate( [1, 2, 3, 4, 5, 6, 6] );
console.log(result); // false, the array is long enough but contains non-unique members
This got me a fair bit closer to what I wanted, but you don’t know which part failed, so it’s harder to give reasonable feedback. I added a set of error messages to validator instances which gets populated after a call to validate():
var result,
myValidator
myValidator = new Validator();
myValidator.add('unique');
myValidator.add('minLength', 6);
myValidator.add('maxLength', 8);
result = myValidator.validate( [1, 2, 3, 4, 5, 6, 6, 8, 9, 10] );
console.log(result); // false, the array is long enough but contains non-unique members
console.log(myValidator.errors);
/*
myValidator.errors == [
'The list must be made up of unique items',
'The list is too long'
]
*/
Again, this is pretty good but even though Validator supports adding messages in any language you want and falling back (by default) to English (see the source code), default error messages still aren’t always what you need. I also added the ability to set a custom error message per “validation”.
var result,
myValidator
myValidator = new Validator();
myValidator.add('unique').message('You are repeating yourself');
myValidator.add('minLength', 6).message('Too tiny!');
myValidator.add('maxLength', 8).message('Too bloated!');
result = myValidator.validate( [1, 2, 3, 4, 5, 6, 6, 8, 9, 10] );
console.log(result); // false, the array is long enough but contains non-unique members
console.log(myValidator.errors);
/*
myValidator.errors == [
'You are repeating yourself',
'Too bloated!'
]
*/
You can also chain calls to add() and message():
var result,
myValidator
myValidator = new Validator();
myValidator.add('unique').message('You are repeating yourself')
.add('minLength', 6).message('Too tiny!')
.add('maxLength', 8).message('Too bloated!');
I’ve added some code which should make it easy to use this as a CommonJS AMD javascript module. In it’s default form you can just include it with a script tag.
If you’re interested in developing Validator itself, the project is tested with Jasmine and documented with JSDoc. Both of these can be run with Rake, and the easiest way to get setup is to use Bundler. Once you’ve got the dependencies you get three rake tasks:
# Start the jasmine server, and open http://localhost:8888/ to run the test suite: $ rake jasmine # Start the jasmine server and also run a browser through the tests automatically: $ rake jasmine:ci # Generate the docs $ rake jsdoc
If you fork the project and add any more validations, please also add tests and docs.