This repository has been archived by the owner on May 7, 2020. It is now read-only.
allow NULL as a legal outcome of the jsonpath transformation #4909
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.
...in case the element really exists and is set to
null
.It doesn't return
null
though (so #4379 is not reverted), but returns the string representation ofUndefType.NULL
instead (i.e."NULL"
).This still does not address the problem which @martinvw's mentioned that in JSON often null-attributes are left out completely. I have no idea how to solve that, except to return always
"NULL"
in case the element was not found (and maybe log a warning).fixes #4870
Signed-off-by: Simon Kaufmann simon.kfm@googlemail.com