chore(deps): update dependency ajv@<6.14.0 to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ajv@<6.14.0 (source)	>=6.14.0 → >=7.2.4

---

Release Notes

ajv-validator/ajv (ajv@<6.14.0)

v7.2.4

Compare Source

Fix #​1515: correctly initialize evaluated properties.

v7.2.3

Compare Source

Remove docs from npm package

v7.2.2

Compare Source

Docs correction
Simplified JSONSchemaType (@​erikbrinkman)
Fix #​1493 - incorrect reporting of missing required property with option ownProperties: true
Fix #​1501 - JTD not working correctly with many properties in the schema

v7.2.1

Compare Source

Add tests and fix parsers compiled with ajv.compileParser from JTD schemas:

• fail on invalid JSON:
  • trailing comma in arrays/objects
  • invalid JSON numbers
  • control characters in strings
• fix parsing of u-escaped characters
• do not fail on duplicate object keys (consistent with JSON.parse)

Compiled parsers are now:

• consistent with JSON.parse in case of invalid JSON
• only parse data that is valid for JTD schema

It is a breaking change for compiled parsers compared with 7.2.0 that was released earlier on the same day.

v7.2.0

Compare Source

strictRequired option (off by default) - to log or fail if properties used in JSON Schema "required" are not defined in "properties" (@​PBug90, #​1403)

Compiled parsers (as fast as JSON.parse on valid JSON, but replace validation and fail much faster on invalid JSON) and serializers (10x+ faster than JSON.stringify) from JSON Type Definition schemas (#​1454) - see examples in javascript and typescript

Please note: there are fixes to compiled parsers in 7.2.1

The website migrated to VuePress and documentation is restructured to make navigating Ajv documentation and learning easier - this is still work in progress, but already some improvement on the information structure. Any feedback/corrections would be very much appreciated!

Improved TypeScript support for JSONSchemaType:

• JTDSchemaType utility type to convert your data type into the type of JTD schema, to simplify its writing and to make sure it is consistent with your data type, with type inference support for ajv methods (@​erikbrinkman, #​1446, #​1456, #​1457, #​1475) - see example here
• Alternatively, you can use JTDDataType utility type to convert your JTD schema type into the type of data (@​erikbrinkman, #​1458) - see this example

Other improvements by @​Fdawgs (#​1466), @​t7yang (#​1472, #​1473), @​koba04 (#​1460)

v7.1.1

Compare Source

Support readonly arrays with JSONSchemaType (@​LinusU, #​1447)

v7.1.0

Compare Source

Support for JSON Type Definition RFC 8927 - a simple schema language provided as an alternative to JSON Schema.

See these docs:

• an informal document on Ajv site
• RFC8927
• choosing schema language - comparison with JSON Schema

Allow ":" in keyword names (#​1421, @​teq0)

v7.0.4

Compare Source

Fix: duplicate functions in standalone validation code with mutually recursive schemas (#​1361)
Fix: reference resolution when base URI change was not applied (#​1414)

v7.0.3

Compare Source

Fixes:

• oneOf error type (#​1368, @​G-Rath)
• remove multiple imports (rollup/plugins#745)

Docs:

• Using in ES5 (#​1364, @​aladdin-add)
• Option strictTypes: false has to be used with json-schema-secure schema (#​1373)

v7.0.2

Compare Source

Remove duplicate functions from standalone validation code (#​1361)

v7.0.1

Compare Source

Update error message for maxLength/minLength keywords

v7.0.0

Compare Source

Please note: this document covers the changes from v6.12.6.

The main changes

• support of JSON Schema draft-2019-09 features: unevaluatedProperties and unevaluatedItems, dynamic recursive references and other additional keywords.
• comprehensive support for standalone validation code - compiling one or multiple schemas to standalone modules with one or multiple exports.
• to reduce the mistakes in JSON schemas and unexpected validation results, strict mode is added - it prohibits ignored or ambiguous JSON Schema elements. See Strict mode and Options for more details
• to make code injection from untrusted schemas impossible, code generation is fully re-written to be type-level safe against code injection.
• to simplify Ajv extensions, the new keyword API that is used by pre-defined keywords is available to user-defined keywords - it is much easier to define any keywords now, especially with subschemas.
• schemas are compiled to ES6 code (ES5 code generation is supported with an option).
• to improve reliability and maintainability the code is migrated to TypeScript.
• separate Ajv classes from draft-07 and draft-2019-09 support with different default imports (see Getting started or v7.0.0-beta.5 for the details).

Please note:

• the support for JSON-Schema draft-04 is removed - if you have schemas using "id" attributes you have to replace them with "$id" (or continue using version 6 that will be supported until 02/28/2021).
• all formats are separated to ajv-formats package - they have to be explicitly added if you use them.
• Ajv instance can only be created with new keyword, as Ajv is now ES6 class.
• browser bundles are automatically published to ajv-dist package (but still available on cdnjs.com).
• order of schema keyword validation changed - keywords that apply to all types (allOf etc.) are now validated first, before the keywords that apply to specific data types. You can still define custom keywords that apply to all types AND are validated after type-specific keywords using option post: true in keyword definition.
• regular expressions in keywords "pattern" and "patternProperties" are now used as if they had unicode "u" flag, as required by JSON Schema specification - it means that some regular expressions that were valid with Ajv v6 are now invalid (and vice versa).

Better TypeScript support:

• Methods compile and compileAsync now return type-guards - see Getting started.
• Method validate is a type-guard.
• Better separation of asynchronous schemas on type level.
• Type utility JSONSchemaType that generates the type for JSON Schema for type interface in the type parameter - it simplifies writing schemas (no unions support at the moment).

API changes:

• addVocabulary - NEW method that allows to add an array of keyword definitions.
• addKeyword - keyword name should be passed as property in definition object, not as the first parameter (old API works with "deprecated" warning). Also "inline" keywords support is removed, code generation keywords can now be defined with "code" keyword - the same definition format that is used by all pre-defined keywords
• Ajv no longer allows to create the instance without new keyword (it is ES6 class).

Added options (and defaults):

• strict: true - strict mode
• strictTypes: "log" - prevent mistakes related to type keywords and keyword applicability (see Strict Types)
• strictTuples: "log" - prevent incomplete tuple schemas (see Prohibit unconstrained tuples)
• allowUnionTypes: false - allow multiple non-null types in "type" keyword
• allowMatchingProperties: false - allow overlap between "properties" and "patternProperties" keywords
• loopEnum: Infinity - optimise validation of enums, similar to loopRequired
• validateFormats: true - enable format validation
• code: {optimize: number|boolean} - control code optimisation
• code: {es5: true} - generate ES5 code, the default is to generate ES6 code.
• code: {lines: true} - add line breaks to generated code - simplifies debugging of compiled schemas when you need it

Changed options:

• keywords - now expects the array of keyword definitions (old API works with "deprecated" warning)

Removed options:

• errorDataPath - was deprecated, now removed.
• format - validateFormats: false can be used instead, old format mode can be chosen via ajv-formats package.
• nullable: nullable keyword is supported by default.
• jsonPointers: JSONPointers are used to report errors by default, jsPropertySyntax: true (deprecated) can be used if old format is needed.
• extendRefs: $ref siblings are validated by default (consistent with draft 2019-09), ignoreKeywordsWithRef (deprecated) can be used instead to ignore $ref siblings.
• missingRefs: now exception is always thrown. Pass empty schema with $id that should be ignored to ajv.addSchema.
• processCode: replaced with code: {process: (code, schemaEnv: object) => string}.
• sourceCode: replaced with code: {source: true}.
• schemaId: removed, as JSON Schema draft-04 is no longer supported.
• strictDefaults, strictKeywords, strictNumbers: it is default now, controlled with strict.
• uniqueItems: '"uniqueItems" keyword is always validated.
• unknownFormats: the same can be achieved by passing true for formats that need to be ignored via ajv.addFormat or formats option.
• cache and serialize: Map is used as cache, schema object as key.

---

Configuration

📅 Schedule: (in timezone Europe/Berlin)

• Branch creation
  • "after 10:00 before 19:00 every weekday except after 13:00 before 14:00"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Thank you for following the naming conventions! 🙏

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	left-pad@​1.3.0

View full report

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 7.x releases. But if you manually upgrade to 7.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using our GitHub Discussions tab for questions.