Jsonschema

Latest version: v4.23.0

Safety actively analyzes 681866 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 25

4.23.0

=======

* Do not reorder dictionaries (schemas, instances) that are printed as part of validation errors.
* Declare support for Py3.13

4.22.0

=======

* Improve ``best_match`` (and thereby error messages from ``jsonschema.validate``) in cases where there are multiple *sibling* errors from applying ``anyOf`` / ``allOf`` -- i.e. when multiple elements of a JSON array have errors, we now do prefer showing errors from earlier elements rather than simply showing an error for the full array (1250).
* (Micro-)optimize equality checks when comparing for JSON Schema equality by first checking for object identity, as ``==`` would.

4.21.1

=======

* Slightly speed up the ``contains`` keyword by removing some unnecessary validator (re-)creation.

4.21.0

=======

* Fix the behavior of ``enum`` in the presence of ``0`` or ``1`` to properly consider ``True`` and ``False`` unequal (1208).
* Special case the error message for ``{min,max}{Items,Length,Properties}`` when they're checking for emptiness rather than true length.

4.20.0

=======

* Properly consider items (and properties) to be evaluated by ``unevaluatedItems`` (resp. ``unevaluatedProperties``) when behind a ``$dynamicRef`` as specified by the 2020 and 2019 specifications.
* ``jsonschema.exceptions.ErrorTree.__setitem__`` is now deprecated.
More broadly, in general users of ``jsonschema`` should never be mutating objects owned by the library.

4.19.2

=======

* Fix the error message for additional items when used with heterogeneous arrays.
* Don't leak the ``additionalItems`` keyword into JSON Schema draft 2020-12, where it was replaced by ``items``.

Page 1 of 25

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.