Toggle table of contents sidebar
jsonschema.protocols¶
typing.Protocol classes for jsonschema interfaces.
The protocol to which all validator classes adhere.
schema – The schema that the validator object will validate with. It is assumed to be valid, and providing an invalid schema can lead to undefined behavior. See Validator.check_schema to validate a schema first.
registry – a schema registry that will be used for looking up JSON references
resolver –
a resolver that will be used to resolve $ref properties (JSON references). If unprovided, one will be created.
Deprecated since version v4.18.0: RefResolver has been deprecated in favor of referencing, and with it, this argument.
format_checker – if provided, a checker which will be used to assert about format properties present in the schema. If unprovided, no format validation is done, and the presence of format within schemas is strictly informational. Certain formats require additional packages to be installed in order to assert against instances. Ensure you’ve installed jsonschema with its extra (optional) dependencies when invoking pip.
Deprecated since version v4.12.0: Subclassing validator classes now explicitly warns this is not part of their public API.
A jsonschema.FormatChecker that will be used when validating format keywords in JSON schemas.
A function which given a schema returns its ID.
An object representing the validator’s meta schema (the schema that describes valid schemas in the given version).
A jsonschema.TypeChecker that will be used when validating type keywords in JSON schemas.
A mapping of validation keywords (strs) to functions that validate the keyword with that name. For more information see Creating or Extending Validator Classes.
Validate the given schema against the validator’s META_SCHEMA.
jsonschema.exceptions.SchemaError – if the schema is invalid
Create a new validator like this one, but with given changes.
Preserves all other attributes, so can be used to e.g. create a validator with a different schema but with the same $ref resolution behavior.
>>> validator = Draft202012Validator({})
>>> validator.evolve(schema={"type": "number"})
Draft202012Validator(schema={'type': 'number'}, format_checker=None)
The returned object satisfies the validator protocol, but may not be of the same concrete class! In particular this occurs when a $ref occurs to a schema with a different $schema than this one (i.e. for a different draft).
>>> validator.evolve(
... schema={"$schema": Draft7Validator.META_SCHEMA["$id"]}
... )
Draft7Validator(schema=..., format_checker=None)
Check if the instance is of the given (JSON Schema) type.
instance – the value to check
type – the name of a known (JSON Schema) type
whether the instance is of the given type
jsonschema.exceptions.UnknownType – if type is not a known type
Check if the instance is valid under the current schema.
whether the instance is valid or not
>>> schema = {"maxItems" : 2}
>>> Draft202012Validator(schema).is_valid([2, 3, 4])
False
Lazily yield each of the validation errors in the given instance.
>>> schema = {
... "type" : "array",
... "items" : {"enum" : [1, 2, 3]},
... "maxItems" : 2,
... }
>>> v = Draft202012Validator(schema)
>>> for error in sorted(v.iter_errors([2, 3, 4]), key=str):
... print(error.message)
4 is not one of [1, 2, 3]
[2, 3, 4] is too long
Deprecated since version v4.0.0: Calling this function with a second schema argument is deprecated. Use Validator.evolve instead.
The schema that will be used to validate instances
Check if the instance is valid under the current schema.
jsonschema.exceptions.ValidationError – if the instance is invalid
>>> schema = {"maxItems" : 2}
>>> Draft202012Validator(schema).validate([2, 3, 4])
Traceback (most recent call last):
...
ValidationError: [2, 3, 4] is too long
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4