The version 5.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of ajv.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes5.0.0
This release is fully backward compatible, but it is likely to require either migrating your schemas (recommended, e.g. using "migrate" command of ajv-cli) or changing your code using Ajv.
You can still use draft-04 and v5 schemas with this release (see Migration guide below).
The changes below are based on 4.11.7 version.
JSON-Schema draft-06 support
Support for boolean schemas: wherever a schema is required, true/false can be used in order to always pass/fail validation.
$id keyword is used as schema URI (previously id).
exclusiveMaximum and exclusiveMinimum keywords must be numbers (previously boolean).
replace boolean form of exclusiveMaximum/Minimum with numeric form
replace Ajv v5 constant with const
Optional changes
replace enum with a single allowed value with const
replace empty schemas with true
replace schemas {"not":{}} with false
You can use "migrate" command of ajv-cli to make these changes to your schemas.
If you need to continue using draft-04 schemas
var ajv =newAjv({
meta:false, // optional, to prevent adding draft-06 meta-schema
extendRefs:true, // optional, current default is to 'fail', spec behaviour is to 'ignore'
unknownFormats:'ignore', // optional, current default is true (fail)// ...
});
var metaSchema =require('ajv/lib/refs/json-schema-draft-04.json');
ajv.addMetaSchema(metaSchema);
ajv._opts.defaultMeta=metaSchema.id;
// optional, using unversioned URI is out of spec, see https://github.com/json-schema-org/json-schema-spec/issues/216ajv._refs['http://json-schema.org/schema'] ='http://json-schema.org/draft-04/schema';
// Optionally you can also disable keywords defined in draft-06ajv.removeKeyword('propertyNames');
ajv.removeKeyword('contains');
ajv.removeKeyword('const');
If you use need to continue using schemas requiring v5 mode of Ajv
var ajv =newAjv({
$data:true,
patternGroups:true,
meta:false, // optional, to prevent adding draft-06 meta-schema
extendRefs:true, // optional, current default is to 'fail', spec behaviour is to 'ignore'
unknownFormats:'ignore', // optional, current default is true (fail)// ...
});
ajv.addMetaSchema(require('ajv/lib/refs/json-schema-draft-04.json'));
ajv._refs['http://json-schema.org/schema'] ='http://json-schema.org/draft-04/schema'; // optional, using unversioned URI is out of specvar metaSchema =require('ajv/lib/refs/json-schema-v5.json');
ajv.addMetaSchema(metaSchema);
ajv._opts.defaultMeta=metaSchema.id;
// optional - to avoid changing the schemasajv.addKeyword('constant', { macro:x=> ({ const: x }) }); // this keyword is renamed to const in draft-06// you need to use version "^2.0.0" of ajv-keywordsrequire('ajv-keywords')(ajv, ['switch', 'patternRequired', 'formatMinimum', 'formatMaximum']);
// Optionally you can also disable propertyNames keyword defined in draft-06ajv.removeKeyword('propertyNames');
There are 144 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 5.0.0 of ajv just got published.
The version 5.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of ajv. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
5.0.0This release is fully backward compatible, but it is likely to require either migrating your schemas (recommended, e.g. using "migrate" command of ajv-cli) or changing your code using Ajv.
You can still use draft-04 and v5 schemas with this release (see Migration guide below).
The changes below are based on 4.11.7 version.
JSON-Schema draft-06 support
true/falsecan be used in order to always pass/fail validation.$idkeyword is used as schema URI (previouslyid).exclusiveMaximumandexclusiveMinimumkeywords must be numbers (previously boolean).See Internet drafts: JSON Schema, JSON Schema Validation.
Migrating from Ajv 4.x.x
Migrate your schemas
It is a recommended approach.
Required changes
idwith$id$schemaexclusiveMaximum/Minimumwith numeric formconstantwithconstOptional changes
enumwith a single allowed value withconsttrue{"not":{}}withfalseYou can use "migrate" command of ajv-cli to make these changes to your schemas.
If you need to continue using draft-04 schemas
If you use need to continue using schemas requiring v5 mode of Ajv
Changes
Validation keywords
Moved/deprecated:
patternRequired.Formats
Methods
compileAsyncmethod returns Promise and supports async loading of meta-schemas (#249, #334).Options
schemaIddetermining whether $id, id or both are used.$datafor $data reference support.ownPropertiessupports all keywords (#197).serializeto replace json-stable-stringify with another function to serialise schemas.meta: falseis used withoutvalidateSchema: false.processCode: function() {}can be used to beautify/transpile generated code.beautify: trueis no longer supported.v5is no longer used.Option defaults changed:
"ignore"- when $ref is used other keywords are ignored (wastrue) (#294).false- do not store source code of validation functions (wastrue) (#309).true- fail schema compilation (was"ignore") (#324).Asynchronous validation
transpileoption support require ajv-async package."co*"(co-wrapped generator functions).processCodeoption. See Options.true).Other
console.warnandconsole.error(#265).Related packages
Compatible versions are:
Commits
The new version differs by 144 commits .
8641c6bversion 5.0.0fde7030Merge pull request #464 from epoberezkin/5.0.021818c7Merge branch 'master' into 5.0.02fc8a64Merge branch 'master' into 5.0.067dd36aversion 5.0.4-beta.3e82b62dMerge branch 'master' into 5.0.0b8fdbd1Merge branch 'gajus-feat/add-url-record-format' into 5.0.08bb21ddMerge branch 'feat/add-url-record-format' of https://github.com/gajus/ajv into gajus-feat/add-url-record-format3b0eee3Merge branch 'master' into 5.0.0cc711fcdocs: migrate schemas with ajv-clid9ee511fix: modifying custom keyword should not update parent data of root data3f9ab64feat: more comprehencive uri-reference format in {format: "full"} mode0b308dbtest: update JSON-Schema-Test-Suite, enable optional/bignum test2daf587version 5.0.4-beta.002f9a15Merge branch 'master' into 5.0.0There are 144 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: