Use project version of ajv-cli in npm:validate
task
#123
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The ajv-cli command line tool is used for validating data files against their JSON schema.
In general, it is preferable, and for some schemas even mandatory, to use the modern versions of ajv-cli. However, support for the "Draft-04" schema specification schema specification was dropped in ajv-cli version 4.0.0. So when working with JSON schemas that specify that draft, it is necessary to use ajv-cli 3.3.0, the last compatible version.
Previously, the
package.json
schema specified the "Draft-04" specification. For this reason, thenpm:validate
task was configured to use [email protected].The
package.json
schema has now been updated to use "Draft-07" (SchemaStore/schemastore@11e62f6). So the code for using [email protected] is removed from the task, and the standard project level version of ajv-cli will now be used by this task.