removed unnecessary check which causes nullable=true, handleNullableFields= true with value=null to fail in all cases except OneOf #554
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.
when nullable = true , handlenullableFields = true and value supplied = null , then getting this failure message
"null found, string expected"
for this example:Data to be created:
Reason appears this unnecessary check for
state.isComplexValidator()
which is true only in case of oneOf . so it suppresses all handleNullableFields configurations causing the above error message.This is related to my latest query on this issue #183