Package Exports
- ajv
- ajv/lib/ajv
- ajv/lib/compile/equal
- ajv/lib/compile/formats
- ajv/lib/compile/formats.js
- ajv/lib/refs/json-schema-draft-04
- ajv/lib/refs/json-schema-draft-04.json
- ajv/package.json
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (ajv) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
ajv - Another JSON schema Validator
TODO
- remote refs
- custom formats (via options)
- schema validation before compilation
- bundle compiled templates (doT will be dev dependency)
Install
npm install ajv
Usage
var ajv = require('ajv')(options);
var validate = ajv.compile(schema);
var valid = validate(data);
if (!valid) console.log(validate.errors);
or
// ...
var valid = ajv.validate(schema, data);
// ...
ajv compiles schemas to functions and caches them in both cases (using stringified schema as a key - using json-stable-stringify), so that the next time the same schema is used (not necessarily the same object instance) it won't be compiled again.
Options
- allErrors: if true, ajv checks all rules collecting all errors, otherwise it will return after the first error (false by default)
- verbose: include the reference to the validated data in the errors (false by default)
- format: if false, the formats won't be validated (true by default)
- uniqueItems: if false,
uniqueItems
keyword will be ignored (true by default, i.e. uniqueItems is checked) - unicode: if false, sting.length will be used and the string lengths with unicode pairs will be "incorrect" because each unicode pair will be counted as two characters (true by default - string lengths are calculated correctly but it is slower)
Tests
git submodule update --init
npm test