@texaryn/schema-json 0.6.2 → 0.6.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +11 -0
- package/README.md +3 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,16 @@
|
|
|
1
1
|
# @texaryn/schema-json
|
|
2
2
|
|
|
3
|
+
## 0.6.3
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- 609ad71: The README states when a schema's own `format` keywords are asserted: in
|
|
8
|
+
Draft 7, including a schema whose `$schema` is absent or unrecognized while the
|
|
9
|
+
fallback is `draft-07`, and never in 2019-09 or 2020-12, where declaring the
|
|
10
|
+
format-assertion vocabulary does not turn it on. The `format` keywords inside a
|
|
11
|
+
published metaschema reached through `$ref` are asserted in every dialect. No
|
|
12
|
+
code changes.
|
|
13
|
+
|
|
3
14
|
## 0.6.2
|
|
4
15
|
|
|
5
16
|
### Patch Changes
|
package/README.md
CHANGED
|
@@ -49,7 +49,7 @@ The returned object implements `SchemaEvaluationPort` from `@texaryn/core`.
|
|
|
49
49
|
| 2019-09 | Supported |
|
|
50
50
|
| 2020-12 | Supported |
|
|
51
51
|
|
|
52
|
-
Dialect support does not mean every keyword generates a form control or that Texaryn provides full specification compliance. See the [JSON Schema support guide](https://texaryn.github.io/texaryn/guides/json-schema-support/) for the capability matrix, projection limits and validation behavior
|
|
52
|
+
Dialect support does not mean every keyword generates a form control or that Texaryn provides full specification compliance. See the [JSON Schema support guide](https://texaryn.github.io/texaryn/guides/json-schema-support/) for the capability matrix, projection limits and validation behavior.
|
|
53
53
|
|
|
54
54
|
The adapter detects the dialect from `$schema`. If `$schema` is absent or unrecognized, the adapter uses `draft-07` by default. You can override the fallback:
|
|
55
55
|
|
|
@@ -59,6 +59,8 @@ const adapter = await createJsonSchemaAdapter(schema, {
|
|
|
59
59
|
})
|
|
60
60
|
```
|
|
61
61
|
|
|
62
|
+
The detected dialect alone decides whether the schema's own `format` keywords are asserted. Draft 7 asserts them, and so does a schema whose `$schema` is absent or unrecognized while the fallback is `draft-07`; 2019-09 and 2020-12 never do, even when the format-assertion vocabulary is declared, and the adapter has no option that changes that. The `format` keywords inside a published metaschema reached through `$ref` are asserted in every dialect.
|
|
63
|
+
|
|
62
64
|
## Projection
|
|
63
65
|
|
|
64
66
|
`project(data)` turns the schema plus current instance data into a framework-neutral `SchemaProjection`.
|