-
-
Notifications
You must be signed in to change notification settings - Fork 299
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
Issue-949: Fixing inconsistencies in output schema #950
Conversation
stan-sb
commented
Jun 19, 2020
- Changing "oneOf" to "anyOf", because basic, detailed and verbose have the same definition, oneOf would fail validation.
- Adding "error" keyword and making either "error" or "errors" required in case "valid" is false.
1. Changing "oneOf" to "anyOf", because basic, detailed and verbose have the same definition, oneOf would fail validation. 2. Adding "error" keyword and making either "error" or "errors" required in case "valid" is false.
#940 also addresses oneOf -> anyOf. |
@karenetheridge has @stan-sb addressed your concerns with his last comment? I'd like to get a review from either you or @gregsdennis and get this merged if it is correct. |
@gregsdennis @karenetheridge any update on this? I'd like to get it merged or rejected, whichever is appropriate. We need to wrap up this draft and this has been open for 3 months now. |
I have no strong feelings. I had used |
output/schema.json
Outdated
@@ -41,7 +44,14 @@ | |||
} | |||
}, | |||
"then": { | |||
"required": [ "errors" ] | |||
"oneOf": [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
anyOf here, too. Don't preclude having both.
Make anyOf (instead of oneOf) consistent.