-
By default, the latest version of JSON Schema will be used when a meta schema is not provided in the
$schema
property. The default schema will be 2020-12 for this release. -
When a schema references an unknown meta schema via
$schema
, a reference error will now be thrown instead of the schema being silently treated as a draft 4 schema.
$schema
matching will now operate on normalise URIs and thus will handle cases when the meta spec or the$schema
URI both contain and don't contain empty trailing fragments as the same meta schema.
-
The validation API may now throw errors if the provided JSON Schema is invalid.
-
The structure of ValidationError has changed to include further information such as the location of the failing instance. ValidationError was previous a String.
-
The failing required validation error message is now emitted for each individual required validation failure.
The following JSON Schema would emit two validation failures, one for missing property name and the other for missing property price when when an empty object was validated.
{ "required": ["name", "price"] }
-
Support for the
minContains
andmaxContains
keywords in JSON Schema draft 2019-09. -
Support for the
uuid
format in JSON Schema draft 2019-09.
-
The failing required validation error message incorrectly specified other found keys were missing under the case where another missing key validation failed. #61
-
Fixed
const
andenum
comparisons where numbers inside collection types wouldn't be compared correctly (and thus[true]
would have been treated as equal to[1]
. -
Fixed
uniqueItems
so that numbers and booleans are not treated equal when found within a collection type (for example unique arrays or objects). -
The
ipv6
format will no longer allow IPv6 addresses containing a zone id. -
Zero terminates floats such as
1.0
will now validate against the integer type.
- Support for Swift <= 4.2 was removed.
ValidationResult.Valid
was renamed toValidationResult.valid
.
- Added support for JSON Schema Draft 6 and 7.
- Support for Swift 4 and 5.
uri
format is now validated.
-
Fixes cases where schemas containing an
enum
with a boolean or number may be incorrectly matched against values which are boolean or numbers.For example,
{ "enum": [1] }
incorrectly validated with values oftrue
and vice-versa. -
Added support for referencing parts using escaped
~
and/
.
- Adds support for Swift 2.2.
- Adds support for Swift Package Manager.