In order to implement strict mode and other new upgrades coming with new AJV version.
What was done?
updated ajv dependency v7
updated base and meta schemas to respect changes
How Has This Been Tested?
Unit tests.
Breaking Changes
definitions is now defined using $defs keyword
JSON Schema strict validation is enabled . Previous contract schemas invalid in case they are not respecting strict mode constraints (reference this link for more information)
Do not allow to use if, then, else, allOf, anyOf, oneOf, not in document root properties
Checklist:
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added or updated relevant unit/integration/functional/e2e tests
[x] I have made corresponding changes to the documentation
For repository code-owners and collaborators only
[x] I have assigned this pull request to a milestone
Issue being fixed or feature implemented
In order to implement strict mode and other new upgrades coming with new AJV version.
What was done?
ajv
dependencyv7
How Has This Been Tested?
Unit tests.
Breaking Changes
definitions
is now defined using$defs
keywordif
,then
,else
,allOf
,anyOf
,oneOf
,not
in document root propertiesChecklist:
For repository code-owners and collaborators only