You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When debugging I can see that the specVersion is set to DRAFT_7 and the SchemaLoader.class config.specVersion is set to DRAFT_7
The issue is when the Schema line is run, it still validates against DRAFT_4. - the schema in debug mode can be seen to drop the "format":"date".
{"type":"object","properties":{"date":{"type":"string"}}}
When I create a custom SchemaLoader as below with the draftV7Support specified:
The text was updated successfully, but these errors were encountered:
tzhoumsm
changed the title
format 'date' not validated against when $schema is set to draft-07
$schema not validated against when a $schema is set
Apr 4, 2018
dateschema.json File:
date.json file containing invalid date:
Code run against:
When debugging I can see that the specVersion is set to DRAFT_7 and the SchemaLoader.class config.specVersion is set to DRAFT_7
The issue is when the Schema line is run, it still validates against DRAFT_4. - the schema in debug mode can be seen to drop the "format":"date".
{"type":"object","properties":{"date":{"type":"string"}}}
When I create a custom SchemaLoader as below with the draftV7Support specified:
Then the "format":"date" appears at the Schema line.
{"type":"object","properties":{"date":{"type":"string","format":"date"}}}
What I don't want to do is create a custom schemaLoader like above as that appears to then validate all schemas against draft07?
Am I doing something wrong when specifying: "$schema": "http://json-schema.org/draft-07/schema#" ?
The text was updated successfully, but these errors were encountered: