Open Whathecode opened 2 years ago
This works partially with a bugfix for json-schema-validator
introduced in 1.0.67. All external references to anchors now use the anchor notation. However, internal anchor references still fail and currently thus still use the full path notation.
The json-schema-validator library we want to use for JSON schema validation does not yet support named anchor lookup for the metaschema we are using (draft 2019/09).
As a workaround, we currently use JSON pointer URIs within our schemas to point to these anchors.
The current locations are:
TriggeredTask.json
to point toTaskControl#Control
DataStreamServiceRequest.json
) to point to definitions within the same fileJsonSchemaTest.kt
to load the reponse schemas of requestsOnce json-schema-validator provides support for this, we can upgrade and replace these references with named anchor references.