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
JSON Schema standard error reporting is verbose (even when using the "basic" format, and more so with the more complex ones). oascomply should log the full error output ("detailed" or "verbose"?), at least on a high logging verbosity. But for the main error report, it should prune the output.
Ideas include:
prune all annotations, except perhaps ones like properties that might help debug (but probably better to leave that for the verbose output log)
if a oneOf or anyOf passed, prune all errors from failing branches
unevaluatedProperties (and to a lesser degree, additionalProperties and similar keywords for array items) cause produce errors when a property/item fails validation and then becomes evaluated by the *Properties* or *Items* keyword when it normally would not be
I think some errors can be repeated in the output as they propagate upwards in some way, need to investigate but I suspect some things can be pruned here
The text was updated successfully, but these errors were encountered:
One thing to do: "if" errors get included in the report, which is useful when figuring out why the wrong one of "then" vs "else" was selected, but they should be moved to a more supplemental area.
JSON Schema standard error reporting is verbose (even when using the "basic" format, and more so with the more complex ones).
oascomply
should log the full error output ("detailed" or "verbose"?), at least on a high logging verbosity. But for the main error report, it should prune the output.Ideas include:
properties
that might help debug (but probably better to leave that for the verbose output log)oneOf
oranyOf
passed, prune all errors from failing branchesunevaluatedProperties
(and to a lesser degree,additionalProperties
and similar keywords for array items) cause produce errors when a property/item fails validation and then becomes evaluated by the*Properties*
or*Items*
keyword when it normally would not beThe text was updated successfully, but these errors were encountered: