ajv - Another JSON Schema Validator
One of the fastest JSON Schema validators for node.js and browser.
It uses precompiled doT templates to generate super-fast validating functions.
JSON Schema standard
ajv implements full JSON Schema draft 4 standard:
- all validation keywords
- full support of remote refs (remote schemas have to be added with
addSchema
or compiled to be available) - support of circular dependencies between schemas
- correct string lengths for strings with unicode pairs (can be turned off)
- formats defined by JSON Schema draft 4 standard and custom formats (can be turned off)
ajv passes all the tests from JSON Schema Test Suite (apart from the one that requires that 1.0
is not an integer).
Benchmarks
Benchmark of the test suite - json-schema-benchmark.
Same benchmark run on faster CPU with node 0.12.
Benchmark of schemas of different complexity by jsck.
Benchmark of individual test cases by z-schema.
Install
npm install ajv
Usage
The fastest validation call:
var Ajv = require('ajv');
var ajv = Ajv(); // options can be passed
var validate = ajv.compile(schema);
var valid = validate(data);
if (!valid) console.log(validate.errors);
or with less code
// ...
var valid = ajv.validate(schema, data);
if (!valid) console.log(ajv.errors);
// ...
or
// ...
ajv.addSchema(schema, 'mySchema');
var valid = ajv.validate('mySchema', data);
if (!valid) console.log(ajv.errorsText());
// ...
ajv compiles schemas to functions and caches them in all 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.
The best performance is achieved when using compiled functions returned by compile
or getSchema
methods (there is no additional function call).
Using in browser
You can require ajv directly from the code you browserify - in this case ajv will be a part of your bundle.
If you need to use ajv in several bundles you can create a separate browserified bundle using bin/create-bundle
script (thanks to siddo420).
Then you need to load ajv in the browser:
<script src="ajv.bundle.js"></script>
Now you can use it as shown above - require
will be global and you can require('ajv')
.
Ajv was tested with these browsers:
Formats
The following formats are supported for string validation with "format" keyword:
There are two modes of format validation: fast
and full
that affect all formats but ipv4
and ipv6
. See Options for details.
You can add additional formats and replace any of the formats above using addFormat method.
You can find patterns used for format validation and the sources that were used in formats.js.
Filtering data
With option removeAdditional
(added by andyscott) you can filter data during the validation.
This option modifies original object.
API
Ajv(Object options) -> Object
Create ajv instance.
All the instance methods below are bound to the instance, so they can be used without the instance.
.compile(Object schema) -> Function<Object data>
Generate validating function and cache the compiled schema for future use.
Validating function returns boolean and has properties errors
with the errors from the last validation (null
if there were no errors) and schema
with the reference to the original schema.
Unless the option validateSchema
is false, the schema will be validated against meta-schema and if schema is invalid the error will be thrown. See options.
.validate(Object schema|String key|String ref, data) -> Boolean
Validate data using passed schema (it will be compiled and cached).
Instead of the schema you can use the key that was previously passed to addSchema
, the schema id if it was present in the schema or any previously resolved reference.
Validation errors will be available in the errors
property of ajv instance (null
if there were no errors).
.addSchema(Array<Object>|Object schema [, String key])
Add schema(s) to validator instance. From version 1.0.0 this method does not compile schemas (but it still validates them). Because of that change, dependencies can be added in any order and circular dependencies are supported. It also prevents unnecessary compilation of schemas that are containers for other schemas but not used as a whole.
Array of schemas can be passed (schemas should have ids), the second parameter will be ignored.
Key can be passed that can be used to reference the schema and will be used as the schema id if there is no id inside the schema. If the key is not passed, the schema id will be used as the key.
Once the schema is added, it (and all the references inside it) can be referenced in other schemas and used to validate data.
Although addSchema
does not compile schemas, explicit compilation is not required - the schema will be compiled when it is used first time.
By default the schema is validated against meta-schema before it is added, and if the schema does not pass validation the exception is thrown. This behaviour is controlled by validateSchema
option.
.addMetaSchema(Object schema [, String key])
Adds meta schema that can be used to validate other schemas. That function should be used instead of addSchema
because there may be instance options that would compile a meta schema incorrectly (at the moment it is removeAdditional
option).
There is no need to explicitely add draft 4 meta schema (http://json-schema.org/draft-04/schema) - it is added by default, unless option meta
is set to false
. You only need to use it if you have a changed meta-schema that you want to use to validate your schemas. See validateSchema
.
.validateSchema(Object schema) -> Boolean
Validates schema. This method should be used to validate schemas rather than validate
due to the inconsistency of uri
format in JSON-Schema standart.
By default this method is called automatically when the schema is added, so you rarely need to use it directly.
If schema doesn't have $schema
property it is validated against draft 4 meta-schema (option meta
should not be false).
If schema has $schema
property then the schema with this id (should be previously added) is used to validate passed schema.
Errors will be available at ajv.errors
.
.getSchema(String key) -> Function<Object data>
Retrieve compiled schema previously added with addSchema
by the key passed to addSchema
or by its full reference (id). Returned validating function has schema
property with the reference to the original schema.
.removeSchema(Object schema|String key|String ref)
Remove added/cached schema. Even if schema is referenced by other schemas it can be safely removed as dependent schemas have local references.
Schema can be removed using key passed to addSchema
, it's full reference (id) or using actual schema object that will be stable-stringified to remove schema from cache.
.addFormat(String name, String|RegExp|Function format)
Add custom format to validate strings. It can also be used to replace pre-defined formats for ajv instance.
Strings are converted to RegExp.
Function should return validation result as true
or false
.
Custom formats can be also added via formats
option.
.errorsText([Array<Object> errors [, Object options]]) -> String
Returns the text with all errors in a String.
Options can have properties separator
(string used to separate errors, ", " by default) and dataVar
(the variable name that dataPaths are prefixed with, "data" by default).
Options
- allErrors: check all rules collecting all errors. Default is to return after the first error.
- removeAdditional: remove additional properties. Default is not to remove. If the option is 'all', then all additional properties are removed, regardless of
additionalProperties
keyword in schema (and no validation is made for them). If the option is true
(or truthy), only additional properties with additionalProperties
keyword equal to false
are removed. If the option is 'failing', then additional properties that fail schema validation will be removed too (where additionalProperties
keyword is schema). - verbose: include the reference to the part of the schema and validated data in errors (false by default).
- format: formats validation mode ('fast' by default). Pass 'full' for more correct and slow validation or
false
not to validate formats at all. E.g., 25:00:00 and 2015/14/33 will be invalid time and date in 'full' mode but it will be valid in 'fast' mode. - formats: an object with custom formats. Keys and values will be passed to
addFormat
method. - schemas: an array or object of schemas that will be added to the instance. If the order is important, pass array. In this case schemas must have IDs in them. Otherwise the object can be passed -
addSchema(value, key)
will be called for each schema in this object. - meta: add meta-schema so it can be used by other schemas (true by default).
- validateSchema: validate added/compiled schemas against meta-schema (true by default).
$schema
property in the schema can either be http://json-schema.org/draft-04/schema or absent (draft-4 meta-schema will be used) or can be a reference to the schema previously added with addMetaSchema
method. If the validation fails, the exception is thrown. Pass "log" in this option to log error instead of throwing exception. Pass false
to skip schema validation. - missingRefs: by default if the reference cannot be resolved during compilation the exception is thrown. Pass 'ignore' to log error during compilation and pass validation. Pass 'fail' to log error and successfully compile schema but fail validation if this rule is checked.
- uniqueItems: validate
uniqueItems
keyword (true by default). - unicode: calculate correct length of strings with unicode pairs (true by default). Pass
false
to use .length
of strings that is faster, but gives "incorrect" lengths of strings with unicode pairs - each unicode pair is counted as two characters. - beautify: format the generated function with js-beautify (the validating function is generated without line-breaks).
npm install js-beautify
to use this option. true
or js-beautify options can be passed. - cache: an optional instance of cache to store compiled schemas using stable-stringified schema as a key. For example, set-associative cache sacjs can be used. If not passed then a simple hash is used which is good enough for the common use case (a limited number of statically defined schemas). Cache should have methods
put(key, value)
, get(key)
and del(key)
.
Tests
npm install
git submodule update --init
npm test
Browser:
bin/prepare-tests
karma start
Contributing
All validation functions are generated using doT templates in dot folder. Templates are precompiled so doT is not a run-time dependency.
bin/compile-dots
- compiles templates to dotjs folder (please use node 0.10 to compile - 0.12 is fully supported but it inserts some empty comments in function parameters when Function constructor is called).
bin/watch-dots
- automatically compiles templates when files in dot folder change
bin/git-hook
- installs symbolic link to pre-commit hook that will compile templates and run tests.
Changes history
1.0.0
Only compile schemas when they are used first time.
Order in which schemas are added is not important.
Circular references are supported.
0.7.0
addShema
no longer returns compiled schema(s).
Improved / fixed compilation of recursive schemas.
If cache instance is supplied it must have put
, get
and del
methods.
0.6.11
Improved/fixed data filtering with removeAdditional
option.
0.6.10
removeAdditional
option allowing to remove additional properties.
1.0.0
addSchema
no longer compiles schemas and its return value is undefined
Dependencies can be added in any order (all dependencies should be present when the schema is compiled though)
Circular dependencies support
0.6.1
Errors for "required" keyword validation include missing properties
Better references resolution in schemas without IDs
0.5.9
cache
option and removeSchema
method
0.5.2
doT is no longer a run-time dependency
ajv can be used in the browser (with browserify)
0.5.0
Schemas are validated against meta-schema before compilation
0.4.1
Custom formats support.
0.4.0
Errors are set to null
if there are no errors (previously empty array).
License
MIT