-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No causing exceptions #33
Comments
I'm having the same issue; I get the message "#: 2 schema violations found" but there are no causing exceptions. |
Thanks guys for reporting it. You may send a PR with a bugfix in
|
I've just committed the bugfix, it will be released with 1.4.0 |
Hi, iam facing the above issue when I call getCausingExceptions() method in ValidationException class. The getCausingExceptions() method returns valid exception list for multiple schema violations, but it returns empty list for a single schema violation? |
I am getting this even in 1.9.2 version. |
@erosb |
@electronABS please post reproduction details (schema, instance json). |
`
`
|
Hi @electronABS I ran a test with your input and got the following output (by calling {
"causingExceptions": [
{
"causingExceptions": [],
"keyword": "required",
"message": "required key [agentId] not found",
"pointerToViolation": "#",
"schemaLocation": "#"
},
{
"causingExceptions": [],
"keyword": "required",
"message": "required key [reportType] not found",
"pointerToViolation": "#",
"schemaLocation": "#"
}
],
"message": "2 schema violations found",
"pointerToViolation": "#",
"schemaLocation": "#"
} Reproduction testcase added in 0d797d0 |
Hi,
I have an error "#: only 1 subschema matches out of 2" but it's not possible to know what exactly caused the error since the getCausingExceptions() returns an empty list.
The text was updated successfully, but these errors were encountered: