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
I noticed that our JSON Schema implementation is doing a simple check for the not, then and else keywords, meaning a schema like {"not":false} would be treated exactly like {}.
I imagine this should matter in some conditions but I can't quite get my head around the double negatives needed.
This does not seem to have been caught by the draft2020-12 tests as of 7950d9e and I see no changes since then to not.json or `if-then-else.json
The text was updated successfully, but these errors were encountered:
I noticed that our JSON Schema implementation is doing a simple check for the
not
,then
andelse
keywords, meaning a schema like{"not":false}
would be treated exactly like{}
.I imagine this should matter in some conditions but I can't quite get my head around the double negatives needed.
This does not seem to have been caught by the
draft2020-12
tests as of 7950d9e and I see no changes since then tonot.json
or `if-then-else.jsonThe text was updated successfully, but these errors were encountered: