| 1 | # JSON Schema Spec Coverage Report
|
| 2 |
|
| 3 | This report lists the keywords of the JSON Schema spec that are covered in the tests. The overall coverage is 84%
|
| 4 |
|
| 5 | ## The JSON Schema Core Vocabulary
|
| 6 |
|
| 7 | Coverage for [The JSON Schema Core Vocabulary](https://json-schema.org/draft/2019-09/json-schema-core.html#rfc.section.8.1) is 55%.
|
| 8 |
|
| 9 | | Keyword | Supported |
|
| 10 | | :----------------- | :-------- |
|
| 11 | | `$anchor` | No |
|
| 12 | | `$comment` | Yes |
|
| 13 | | `$defs` | Yes |
|
| 14 | | `$id` | Yes |
|
| 15 | | `$recursiveAnchor` | No |
|
| 16 | | `$recursiveRef` | No |
|
| 17 | | `$ref` | Yes |
|
| 18 | | `$schema` | Yes |
|
| 19 | | `$vocabulary` | No |
|
| 20 |
|
| 21 | ## A Vocabulary for Applying Subschemas
|
| 22 |
|
| 23 | Coverage for [A Vocabulary for Applying Subschemas](https://json-schema.org/draft/2019-09/json-schema-core.html#rfc.section.9) is 58%.
|
| 24 |
|
| 25 | | Keyword | Supported |
|
| 26 | | :---------------------- | :-------- |
|
| 27 | | `additionalItems` | Yes |
|
| 28 | | `additionalProperties` | Yes |
|
| 29 | | `allOf` | Yes |
|
| 30 | | `anyOf` | Yes |
|
| 31 | | `contains` | Yes |
|
| 32 | | `dependentSchemas` | No |
|
| 33 | | `else` | No |
|
| 34 | | `if` | No |
|
| 35 | | `items` | Yes |
|
| 36 | | `not` | Yes |
|
| 37 | | `oneOf` | Yes |
|
| 38 | | `patternProperties` | Yes |
|
| 39 | | `properties` | Yes |
|
| 40 | | `propertyNames` | No |
|
| 41 | | `then` | No |
|
| 42 | | `unevaluatedItems` | No |
|
| 43 | | `unevaluatedProperties` | No |
|
| 44 |
|
| 45 | ## Validation Keywords for Any Instance Type
|
| 46 |
|
| 47 | Coverage for [Validation Keywords for Any Instance Type](https://json-schema.org/draft/2019-09/json-schema-validation.html#rfc.section.6.1) is 100%.
|
| 48 |
|
| 49 | | Keyword | Supported |
|
| 50 | | :------ | :-------- |
|
| 51 | | `const` | Yes |
|
| 52 | | `enum` | Yes |
|
| 53 | | `type` | Yes |
|
| 54 |
|
| 55 | ## Validation Keywords for Numeric Instances
|
| 56 |
|
| 57 | Coverage for [Validation Keywords for Numeric Instances](https://json-schema.org/draft/2019-09/json-schema-validation.html#rfc.section.6.2) is 100%.
|
| 58 |
|
| 59 | | Keyword | Supported |
|
| 60 | | :----------------- | :-------- |
|
| 61 | | `exclusiveMaximum` | Yes |
|
| 62 | | `exclusiveMinimum` | Yes |
|
| 63 | | `maximum` | Yes |
|
| 64 | | `minimum` | Yes |
|
| 65 | | `multipleOf` | Yes |
|
| 66 |
|
| 67 | ## Validation Keywords for Strings
|
| 68 |
|
| 69 | Coverage for [Validation Keywords for Strings](https://json-schema.org/draft/2019-09/json-schema-validation.html#rfc.section.6.3) is 100%.
|
| 70 |
|
| 71 | | Keyword | Supported |
|
| 72 | | :---------- | :-------- |
|
| 73 | | `maxLength` | Yes |
|
| 74 | | `minLength` | Yes |
|
| 75 | | `pattern` | Yes |
|
| 76 |
|
| 77 | ## Validation Keywords for Arrays
|
| 78 |
|
| 79 | Coverage for [Validation Keywords for Arrays](https://json-schema.org/draft/2019-09/json-schema-validation.html#rfc.section.6.4) is 100%.
|
| 80 |
|
| 81 | | Keyword | Supported |
|
| 82 | | :------------ | :-------- |
|
| 83 | | `maxContains` | Yes |
|
| 84 | | `maxItems` | Yes |
|
| 85 | | `minContains` | Yes |
|
| 86 | | `minItems` | Yes |
|
| 87 | | `uniqueItems` | Yes |
|
| 88 |
|
| 89 | ## Validation Keywords for Objects
|
| 90 |
|
| 91 | Coverage for [Validation Keywords for Objects](https://json-schema.org/draft/2019-09/json-schema-validation.html#rfc.section.6.5) is 75%.
|
| 92 |
|
| 93 | | Keyword | Supported |
|
| 94 | | :------------------ | :-------- |
|
| 95 | | `dependentRequired` | No |
|
| 96 | | `maxProperties` | Yes |
|
| 97 | | `minProperties` | Yes |
|
| 98 | | `required` | Yes |
|
| 99 |
|
| 100 | ## Defined Formats
|
| 101 |
|
| 102 | Coverage for [Defined Formats](https://json-schema.org/draft/2019-09/json-schema-validation.html#rfc.section.7.3) is 100%.
|
| 103 |
|
| 104 | | Keyword | Supported |
|
| 105 | | :---------------------- | :-------- |
|
| 106 | | `date` | Yes |
|
| 107 | | `date-time` | Yes |
|
| 108 | | `duration` | Yes |
|
| 109 | | `email` | Yes |
|
| 110 | | `hostname` | Yes |
|
| 111 | | `idn-email` | Yes |
|
| 112 | | `idn-hostname` | Yes |
|
| 113 | | `ipv4` | Yes |
|
| 114 | | `ipv6` | Yes |
|
| 115 | | `iri` | Yes |
|
| 116 | | `iri-reference` | Yes |
|
| 117 | | `json-pointer` | Yes |
|
| 118 | | `regex` | Yes |
|
| 119 | | `relative-json-pointer` | Yes |
|
| 120 | | `time` | Yes |
|
| 121 | | `uri` | Yes |
|
| 122 | | `uri-reference` | Yes |
|
| 123 | | `uri-template` | Yes |
|
| 124 | | `uuid` | Yes |
|
| 125 |
|
| 126 | ## A Vocabulary for the Contents of String-Encoded Data
|
| 127 |
|
| 128 | Coverage for [A Vocabulary for the Contents of String-Encoded Data](https://json-schema.org/draft/2019-09/json-schema-validation.html#rfc.section.8) is 100%.
|
| 129 |
|
| 130 | | Keyword | Supported |
|
| 131 | | :----------------- | :-------- |
|
| 132 | | `contentEncoding` | Yes |
|
| 133 | | `contentMediaType` | Yes |
|
| 134 | | `contentSchema` | Yes |
|
| 135 |
|
| 136 | ## A Vocabulary for Basic Meta-Data Annotations
|
| 137 |
|
| 138 | Coverage for [A Vocabulary for Basic Meta-Data Annotations](https://json-schema.org/draft/2019-09/json-schema-validation.html#rfc.section.9) is 100%.
|
| 139 |
|
| 140 | | Keyword | Supported |
|
| 141 | | :------------ | :-------- |
|
| 142 | | `default` | Yes |
|
| 143 | | `deprecated` | Yes |
|
| 144 | | `description` | Yes |
|
| 145 | | `examples` | Yes |
|
| 146 | | `readOnly` | Yes |
|
| 147 | | `title` | Yes |
|
| 148 | | `writeOnly` | Yes |
|