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.
If the instance value is a string, this property defines that the string SHOULD be interpreted as binary data and decoded using the encoding named by this property. RFC 2045, Sec 6.1 [RFC2045] lists the possible values for this property.
The value of this property must be a media type, as defined by RFC 2046 [RFC2046]. This property defines the media type of instances which this schema defines.
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.
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.
A string value can be RELATIVE_JSON_POINTER, JSON_POINTER, UUID, REGEX, IPV6, IPV4, HOSTNAME, EMAIL, URL, URI_TEMPLATE, URI_REFERENCE, URI, TIME, DATE,
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.
A string instance is valid against this keyword if its length is less than, or equal to, the value of this keyword. The length of a string instance is defined as the number of its characters as defined by RFC 7159 [RFC7159].
A string instance is valid against this keyword if its length is greater than, or equal to, the value of this keyword. The length of a string instance is defined as the number of its characters as defined by RFC 7159 [RFC7159].
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}
This string SHOULD be a valid regular expression, according to the ECMA 262 regular expression dialect. A string instance is considered valid if the regular expression matches the instance successfully.
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 $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
It MUST be a non-empty array. Each item of the array MUST be a valid JSON Schema.
{ allOf: [ {} ] }
https://json-schema.org/latest/json-schema-validation.html#rfc.section.6.7.1