improve not_null
and null
functions
#83
Merged
+160
−9
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.
Fixes #76
Fixes #71
null
checks whether the DynamicValue represents a literalnull
with no known type. This behavior conflicted with cross-object validation, where the type is known, and the underlying value needs to be checked to see if it evaluates to null. 9725ed fixes this.not_null
, we’re enabling cross-object validation by first determining if we’re dealing with a literalnull
value. If not, the underlying value is then checked to confirm whether it isnull
or not.