It MUST be a non-empty array. Each item of the array MUST be a valid JSON Schema.
It MUST be a non-empty array. Each item of the array MUST be a valid JSON Schema.
The value of this keyword MAY be of any type, including null.
Make copy of current schema with modified values
Add custom validation functions. Since custom validators didn't supported by JSON Schema, I used AJV custom keywords to add such functionality
There are no restrictions placed on the value of this keyword.
The "definitions" keywords provides a standardized location for schema authors to inline re-usable JSON Schemas into a more general schema. There are no restrictions placed on the values within the array.
This keyword specifies rules that are evaluated if the instance is an object and contains a certain property. This keyword's value MUST be an object. Each property specifies a dependency. Each dependency value MUST be an array or a valid JSON Schema. If the dependency value is a subschema, and the dependency key is a property in the instance, the entire instance must validate against the dependency value. If the dependency value is an array, each element in the array, if any, MUST be a string, and MUST be unique. If the dependency key is a property in the instance, each of the items in the dependency value must be a property that exists in the instance.
It can be used to decorate a user interface with information about the data produced by this user interface. A description provides explanation about the purpose of the instance described by the schema.
Validate provided data with current schema using ajv, if validation failed function will throw error
The value of this keyword MUST be an array. This array SHOULD have at least one element. Elements in the array SHOULD be unique.
The value of this keyword MUST be an array. There are no restrictions placed on the values within the array.
It defines a URI for the schema, and the base URI that other URI references within the schema are resolved against.
an #id
This validation outcome of this keyword's subschema has no direct effect on the overall validation result. Rather, it controls which of the "then" or "else" keywords are evaluated. When "if" is present, and the instance successfully validates against its subschema, then validation succeeds against this keyword if the instance also successfully validates against this keyword's subschema.
When "if" is present, and the instance fails to validate against its subschema, then validation succeeds against this keyword if the instance successfully validates against this keyword's subschema.
An object instance is valid against "maxProperties" if its number of properties is less than, or equal to, the value of this keyword.
An object instance is valid against "minProperties" if its number of properties is greater than, or equal to, the value of this keyword.
It MUST be a valid JSON Schema.
It MUST be a non-empty array. Each item of the array MUST be a valid JSON Schema.
Make schema optional in {ObjectSchema}
Return new ObjectSchema with removed required fields (recursively)
Each property name of this object SHOULD be a valid regular expression, according to the ECMA 262 regular expression dialect. Each property value of this object MUST be a valid JSON Schema. This keyword determines how child instances validate for objects, and does not directly validate the immediate instance itself. Validation of the primitive instance type against this keyword always succeeds. Validation succeeds if, for each instance name that matches any regular expressions that appear as a property name in this keyword's value, the child instance for that name successfully validates against each schema that corresponds to a matching regular expression.
The value of "properties" MUST be an object. Each value of this object MUST be a valid JSON Schema
If the instance is an object, this keyword validates if every property name in the instance validates against the provided schema. Note the property name that the schema is testing will always be a string.
Because the differences between JSON Schemas and Open API (Swagger) it can be handy to arbitrary modify the schema injecting a fragment
an arbitrary JSON Schema to inject
The value must be a valid id e.g. #properties/foo
Set required array
Set $schema property
It can be used to decorate a user interface with information about the data produced by this user interface. A title will preferably be short.
Validate provided data with current schema using ajv, does not throw errors
It returns all the schema values
Generated using TypeDoc
This keyword determines how child instances validate for objects, and does not directly validate the immediate instance itself. Validation with "additionalProperties" applies only to the child values of instance names that do not match any names in "properties", and do not match any regular expression in "patternProperties". For all such properties, validation succeeds if the child instance validates against the "additionalProperties" schema. Omitting this keyword has the same behavior as an empty schema.
https://json-schema.org/latest/json-schema-validation.html#rfc.section.6.5.6