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
For reference, this exact pair validates with Ruby's json-schema.
However, with json-schema-validator (2.2.10) I get:
instance failed to match exactly one schema (matched 3 out of 3)
There are two three-way oneOfs in this schema:
A case distinction over patient, physician, and staff (see top-level schema) -- but those schemas (given by reference) have mutually exclusive singleton enum properties, e.g.
"memberType": {
"enum": ["patient"]
}
for patient, and similar for the other two types.
Different combinations of method and methodId in the referenced member-key schema. There, we have three cases like so:
The following pair should validate:
Schema
JSON:
For reference, this exact pair validates with Ruby's json-schema.
However, with
json-schema-validator
(2.2.10) I get:There are two three-way
oneOf
s in this schema:A case distinction over
patient
,physician
, andstaff
(see top-level schema) -- but those schemas (given by reference) have mutually exclusive singletonenum
properties, e.g.for
patient
, and similar for the other two types.Different combinations of
method
andmethodId
in the referencedmember-key
schema. There, we have three cases like so:Again, we see that the three cases are mutually exclusive.
In summary, it is impossible for any JSON to cause this error (and the given one certainly doesn't),
There must be a bug in the validator.
The text was updated successfully, but these errors were encountered: