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
It seems that if there are multiple oneOf subschemas which share the same field and one has a default and the others do not then the default is always used no matter which subschema is matched. This feels like a defect?
This is with version 1.14.1.
It seems that if there are multiple oneOf subschemas which share the same field and one has a default and the others do not then the default is always used no matter which subschema is matched. This feels like a defect?
eg. schema:
Valid (correctly):
Should not be valid but is:
because the B kind takes the default from the A oneOf.
The text was updated successfully, but these errors were encountered: