Better support for null values (#130)
#131
Merged
Conversation
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
Member
Member
|
Can you also add some docs in the readme about nullable? |
Contributor
Author
jtassin
force-pushed
the
feature/better-null-support
branch
from
a9205c9 to
18b24ae
Compare
jtassin
force-pushed
the
feature/better-null-support
branch
from
18b24ae to
209a343
Compare
Contributor
Author
|
Here comes a few docs and a test case on #130 issue. |
Member
|
Thanks you very much! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Support of the
nullableoption of ajv (Open API 3 specification) on object.An object declared nullable can have a null value.
Today, a null object stringified lead to this error:
As described in the issue #130