Skip to content
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

Merged
merged 1 commit into from Jan 14, 2018

Conversation

sjsf
Copy link
Contributor

@sjsf sjsf commented Jan 12, 2018

...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 of UndefType.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

...in case the element really exists and is set to NULL.

fixes eclipse-archived#4870
Signed-off-by: Simon Kaufmann <simon.kfm@googlemail.com>
@maggu2810 maggu2810 merged commit 2602f08 into eclipse-archived:master Jan 14, 2018
dgajic pushed a commit to dgajic/smarthome that referenced this pull request Jan 27, 2018
…-archived#4909)

...in case the element really exists and is set to NULL.

fixes eclipse-archived#4870
Signed-off-by: Simon Kaufmann <simon.kfm@googlemail.com>
@sjsf sjsf deleted the jsonPathNull branch February 8, 2018 06:59
@htreu htreu added this to the 0.10.0 milestone Oct 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Jsonpath transformation doesn't work with null values in json data.
3 participants