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
Yeah, the same is true when type: ['null', 'string'], enum: ['a', 'b'], null is not accepted. Unfortunately I think that this is a part of the JSON Schema specification so I'm not sure that we could change it.
If someone could quote the spec on how this should be handled I'd be happy to fix it 👍
If a field is
undefined
and the schema specifies it as being an enum, it errors out saying"must be an enum value"
.I think the logical approach here would be to skip that field unless
isRequired
is set totrue
on it as wellThe text was updated successfully, but these errors were encountered: