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
While wanting to determine programmatically why allOf and oneOf constraints are failing, I'm really wishing that the sub-schema paths that are matched could be returned. For example, given the schema below, and this input:
Currently the message returned is: "The property '#/' of type Hash did not match all of the required schemas in schema ..." Having the more specific validation failure path would allow clients to determine a closer neighborhood of failure in order to provide better feedback to users.
The text was updated successfully, but these errors were encountered:
While wanting to determine programmatically why allOf and oneOf constraints are failing, I'm really wishing that the sub-schema paths that are matched could be returned. For example, given the schema below, and this input:
an error message like this would be useful: "Data does not match any schemas from /allOf/1/oneOf" (derived from http://jsonvalidate.com/)
Currently the message returned is: "The property '#/' of type Hash did not match all of the required schemas in schema ..." Having the more specific validation failure path would allow clients to determine a closer neighborhood of failure in order to provide better feedback to users.
The text was updated successfully, but these errors were encountered: