You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we specify JSONPath like $.['a', 'b'] and proocess JSON that miss at least one of those properties, the another one will be replaced with an empty object, e.g.
{"a": 1}
on input, and
{"a": 1, "b": {}}
on output.
This can break downstream consumers as b is supposed to be non-object.
It seems to be regression since R117, but cannot see the reason yet, no major changes has been made in PII enrichment and JSONPath lib remained on the same 2.4.0 version.
If we specify JSONPath like
$.['a', 'b']
and proocess JSON that miss at least one of those properties, the another one will be replaced with an empty object, e.g.on input, and
on output.
This can break downstream consumers as
b
is supposed to be non-object.It seems to be regression since R117, but cannot see the reason yet, no major changes has been made in PII enrichment and JSONPath lib remained on the same 2.4.0 version.
It seems we just re-introduced snowplow/snowplow#3636 during R118 refactoring.
The text was updated successfully, but these errors were encountered: