-
Notifications
You must be signed in to change notification settings - Fork 203
Handle anyOf, allOf, oneOf and not schema keywords #42
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
Closed
Closed
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
fa21953
validate oneOf schemas
fenollp 72f940d
add some little unit tests
fenollp ed75a27
fix some wrong validation code
fenollp 528675e
also do anyOf and allOf
fenollp c6c62c1
handle not too
fenollp e840429
never unexpectedly raise FunctionClauseError in validate/4
fenollp a064054
fix enum validation
fenollp b477928
show value on failing pattern
fenollp e816240
really fix handling of nullable
fenollp File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
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.
Can you clarify this comment?
From https://swagger.io/docs/specification/data-models/data-types/:
My interpretation is that the value must match the schema or be
null
, not anything.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.
Yes this is also my interpretation.
However the schema in
{"nullable": true}
is{}
which is the schema that matches anything. Do you want me to remove that comment maybe?I'd be much happier if we'd use
ex_json_schema
instead of rolling out our own schema handling...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.
Ah I get it now after reading https://swagger.io/docs/specification/data-models/data-types/#any. Any type is allowed when no
type
is specified, andnullable: true
additionally allowsnull
.