z-schema 3.18.1 → 3.19.0

package/README.md

@@ -1,19 +1,20 @@
+# z-schema validator
+
 [![npm version](https://badge.fury.io/js/z-schema.svg)](http://badge.fury.io/js/z-schema)
 [![bower version](https://badge.fury.io/bo/z-schema.svg)](http://badge.fury.io/bo/z-schema)
 [![build status](https://travis-ci.org/zaggino/z-schema.svg?branch=master)](https://travis-ci.org/zaggino/z-schema)
 [![coverage status](https://coveralls.io/repos/zaggino/z-schema/badge.svg)](https://coveralls.io/r/zaggino/z-schema)
 
+[![Greenkeeper badge](https://badges.greenkeeper.io/zaggino/z-schema.svg)](https://greenkeeper.io/)
 [![dependencies Status](https://david-dm.org/zaggino/z-schema/status.svg)](https://david-dm.org/zaggino/z-schema)
 [![devDependencies Status](https://david-dm.org/zaggino/z-schema/dev-status.svg)](https://david-dm.org/zaggino/z-schema?type=dev)
 [![optionalDependencies Status](https://david-dm.org/zaggino/z-schema/optional-status.svg)](https://david-dm.org/zaggino/z-schema?type=optional)
 
-#z-schema validator
-
 [![NPM](https://nodei.co/npm/z-schema.png?downloads=true&downloadRank=true)](https://nodei.co/npm/z-schema/)
 
 - version 3.0 runs also in the browsers now, run tests yourself [here](https://rawgit.com/zaggino/z-schema/master/test/SpecRunner.html)
 
-#Topics
+# Topics
 
 - [Usage](#usage)
 - [Features](#features)
@@ -21,16 +22,16 @@
 - [Benchmarks](#benchmarks)
 - [Contributors](#contributors)
 
-#Usage
+# Usage
 
 Validator will try to perform sync validation when possible for speed, but supports async callbacks when they are necessary.
 
-##Development:
+## Development:
 
 These repository has several submodules and should be cloned as follows:
 >git clone **--recursive** https://github.com/zaggino/z-schema.git
 
-##CLI:
+## CLI:
 
 ```
 npm install --global z-schema
@@ -40,7 +41,7 @@ z-schema mySchema.json myJson.json
 z-schema --strictMode mySchema.json myJson.json
 ```
 
-##NodeJS:
+## NodeJS:
 
 ```javascript
 var ZSchema = require("z-schema");
@@ -48,7 +49,7 @@ var options = ... // see below for possible option values
 var validator = new ZSchema(options);
 ```
 
-##Sync mode:
+## Sync mode:
 
 ```javascript
 var valid = validator.validate(json, schema);
@@ -59,7 +60,7 @@ var errors = validator.getLastErrors();
 ...
 ```
 
-##Async mode:
+## Async mode:
 
 ```javascript
 validator.validate(json, schema, function (err, valid) {
@@ -67,7 +68,7 @@ validator.validate(json, schema, function (err, valid) {
 });
 ```
 
-##Browser:
+## Browser:
 
 ```html
 <script type="text/javascript" src="../dist/ZSchema-browser-min.js"></script>
@@ -78,7 +79,7 @@ validator.validate(json, schema, function (err, valid) {
 </script>
 ```
 
-##Remote references and schemas:
+## Remote references and schemas:
 
 In case you have some remote references in your schemas, you have to download those schemas before using validator.
 Otherwise you'll get ```UNRESOLVABLE_REFERENCE``` error when trying to compile a schema.
@@ -116,7 +117,7 @@ ZSchema.setSchemaReader(function (uri) {
 });
 ```
 
-#Features
+# Features
 
 - [Validate against subschema](#validate-against-subschema)
 - [Compile arrays of schemas and use references between them](#compile-arrays-of-schemas-and-use-references-between-them)
@@ -142,7 +143,7 @@ ZSchema.setSchemaReader(function (uri) {
 - [Set validator to collect as many errors as possible](#breakonfirsterror)
 - [Report paths in errors as arrays so they can be processed easier](#reportpathasarray)
 
-##Validate against subschema
+## Validate against subschema
 
 In case you don't want to split your schema into multiple schemas using reference for any reason, you can use option schemaPath when validating:
 
@@ -152,7 +153,7 @@ var valid = validator.validate(cars, schema, { schemaPath: "definitions.car.defi
 
 See more details in the [test](/test/spec/schemaPathSpec.js).
 
-##Compile arrays of schemas and use references between them
+## Compile arrays of schemas and use references between them
 
 You can use validator to compile an array of schemas that have references between them and then validate against one of those schemas:
 
@@ -203,7 +204,7 @@ var valid = validator.validate(data, schemas[2]);
 // valid === true
 ```
 
-##Register a custom format
+## Register a custom format
 
 You can register any format of your own. Your sync validator function should always respond with a boolean:
 
@@ -222,17 +223,17 @@ ZSchema.registerFormat("xstring", function (str, callback) {
     }, 1);
 });
 ```
-##Helper method to check the formats that have been registered
+## Helper method to check the formats that have been registered
 ```javascript
 var registeredFormats = ZSchema.getRegisteredFormats();
 //registeredFormats will now contain an array of all formats that have been registered with z-schema
 ```
-##Automatic downloading of remote schemas
+## Automatic downloading of remote schemas
 
 Automatic downloading of remote schemas was removed from version ```3.x``` but is still possible with a bit of extra code,
 see [this test](test/spec/AutomaticSchemaLoadingSpec.js) for more information on this.
 
-##Prefill default values to object using format
+## Prefill default values to object using format
 
 Using format, you can pre-fill values of your choosing into the objects like this:
 
@@ -253,9 +254,9 @@ validator.validate(data, schema);
 // data.hello === "world"
 ```
 
-#Options
+# Options
 
-##asyncTimeout
+## asyncTimeout
 
 Defines a time limit, which should be used when waiting for async tasks like async format validators to perform their validation,
 before the validation fails with an ```ASYNC_TIMEOUT``` error.
@@ -266,7 +267,7 @@ var validator = new ZSchema({
 });
 ```
 
-##noEmptyArrays
+## noEmptyArrays
 
 When true, validator will assume that minimum count of items in any ```array``` is 1, except when ```minItems: 0``` is explicitly defined.
 
@@ -276,7 +277,7 @@ var validator = new ZSchema({
 });
 ```
 
-##noEmptyStrings
+## noEmptyStrings
 
 When true, validator will assume that minimum length of any string to pass type ```string``` validation is 1, except when ```minLength: 0``` is explicitly defined.
 
@@ -286,7 +287,7 @@ var validator = new ZSchema({
 });
 ```
 
-##noTypeless
+## noTypeless
 
 When true, validator will fail validation for schemas that don't specify a ```type``` of object that they expect.
 
@@ -296,7 +297,7 @@ var validator = new ZSchema({
 });
 ```
 
-##noExtraKeywords
+## noExtraKeywords
 
 When true, validator will fail for schemas that use keywords not defined in JSON Schema specification and doesn't provide a parent schema in ```$schema``` property to validate the schema.
 
@@ -306,7 +307,7 @@ var validator = new ZSchema({
 });
 ```
 
-##assumeAdditional
+## assumeAdditional
 
 When true, validator assumes that additionalItems/additionalProperties are defined as false so you don't have to manually fix all your schemas.
 
@@ -324,7 +325,7 @@ var validator = new ZSchema({
 });
 ```
 
-##forceAdditional
+## forceAdditional
 
 When true, validator doesn't validate schemas where additionalItems/additionalProperties should be defined to either true or false.
 
@@ -334,7 +335,7 @@ var validator = new ZSchema({
 });
 ```
 
-##forceItems
+## forceItems
 
 When true, validator doesn't validate schemas where ```items``` are not defined for ```array``` type schemas.
 This is to avoid passing anything through an array definition.
@@ -345,7 +346,7 @@ var validator = new ZSchema({
 });
 ```
 
-##forceMinItems
+## forceMinItems
 
 When true, validator doesn't validate schemas where ```minItems``` is not defined for ```array``` type schemas.
 This is to avoid passing zero-length arrays which application doesn't expect to handle.
@@ -356,7 +357,7 @@ var validator = new ZSchema({
 });
 ```
 
-##forceMaxItems
+## forceMaxItems
 
 When true, validator doesn't validate schemas where ```maxItems``` is not defined for ```array``` type schemas.
 This is to avoid passing arrays with unlimited count of elements which application doesn't expect to handle.
@@ -367,7 +368,7 @@ var validator = new ZSchema({
 });
 ```
 
-##forceMinLength
+## forceMinLength
 
 When true, validator doesn't validate schemas where ```minLength``` is not defined for ```string``` type schemas.
 This is to avoid passing zero-length strings which application doesn't expect to handle.
@@ -379,7 +380,7 @@ var validator = new ZSchema({
 ```
 
 
-##forceMaxLength
+## forceMaxLength
 
 When true, validator doesn't validate schemas where ```maxLength``` is not defined for ```string``` type schemas.
 This is to avoid passing extremly large strings which application doesn't expect to handle.
@@ -390,7 +391,7 @@ var validator = new ZSchema({
 });
 ```
 
-##forceProperties
+## forceProperties
 
 When true, validator doesn't validate schemas where ```properties``` or ```patternProperties``` is not defined for ```object``` type schemas.
 This is to avoid having objects with unexpected properties in application.
@@ -401,7 +402,7 @@ var validator = new ZSchema({
 });
 ```
 
-##ignoreUnresolvableReferences
+## ignoreUnresolvableReferences
 
 When true, validator doesn't end with error when a remote reference is unreachable. **This setting is not recommended in production outside of testing.**
 
@@ -411,7 +412,7 @@ var validator = new ZSchema({
 });
 ```
 
-##strictUris
+## strictUris
 
 When true, all strings of format ```uri``` must be an absolute URIs and not only URI references. See more details in [this issue](https://github.com/zaggino/z-schema/issues/18).
 
@@ -421,17 +422,30 @@ var validator = new ZSchema({
 });
 ```
 
-##strictMode
+## strictMode
 
 Strict mode of z-schema is currently equal to the following:
 
+```javascript
+if (this.options.strictMode === true) {
+    this.options.forceAdditional  = true;
+    this.options.forceItems       = true;
+    this.options.forceMaxLength   = true;
+    this.options.forceProperties  = true;
+    this.options.noExtraKeywords  = true;
+    this.options.noTypeless       = true;
+    this.options.noEmptyStrings   = true;
+    this.options.noEmptyArrays    = true;
+}
+```
+
 ```javascript
 var validator = new ZSchema({
     strictMode: true
 });
 ```
 
-##breakOnFirstError
+## breakOnFirstError
 
 By default, z-schema stops validation after the first error is found. With this you can tell it to continue validating anyway:
 
@@ -441,7 +455,7 @@ var validator = new ZSchema({
 });
 ```
 
-##reportPathAsArray
+## reportPathAsArray
 
 Report error paths as an array of path segments instead of a string:
 
@@ -451,20 +465,7 @@ var validator = new ZSchema({
 });
 ```
 
-```javascript
-if (this.options.strictMode === true) {
-    this.options.forceAdditional  = true;
-    this.options.forceItems       = true;
-    this.options.forceMaxLength   = true;
-    this.options.forceProperties  = true;
-    this.options.noExtraKeywords  = true;
-    this.options.noTypeless       = true;
-    this.options.noEmptyStrings   = true;
-    this.options.noEmptyArrays    = true;
-}
-```
-
-##ignoreUnknownFormats
+## ignoreUnknownFormats
 
 By default, z-schema reports all unknown formats, formats not defined by JSON Schema and not registered using
 `ZSchema.registerFormat`, as an error.  But the
@@ -478,7 +479,7 @@ var validator = new ZSchema({
 });
 ```
 
-##customValidator
+## customValidator
 
 **Warning**: Use only if know what you are doing. Always consider using [custom format](#register-a-custom-format) before using this option.
 
@@ -565,7 +566,7 @@ console.log(validator.getLastErrors())
 ```
 **Note:** before creating your own keywords you should consider all compatibility issues.
 
-#Benchmarks
+# Benchmarks
 
 So how does it compare to version 2.x and others?
 
@@ -573,7 +574,7 @@ So how does it compare to version 2.x and others?
 
 [rawgithub.com/zaggino/z-schema/master/benchmark/results.html](https://rawgithub.com/zaggino/z-schema/master/benchmark/results.html)
 
-#Contributors
+# Contributors
 
 Thanks for contributing to: