Skip to content

Conversation

@gpsamson
Copy link
Contributor

@gpsamson gpsamson commented Aug 8, 2019

What does this PR do?

  • Excludes nested non-null objects from customer user attributes in identify method
  • Excludes non-null objects from custom event properties in track method
  • Conditionally set user-related traits (ID, name, address, etc.)
  • Use serviceWorkerLocation from settings if it is available.

This is a combination of #153, #167, #170, #176 ! Three (3) changes were originally written by @NikoRoberts but had to be reverted and a bad conditional had to be fixed. One change (#176) is originally written by @mericsson.

Are there breaking changes in this PR?
Negative

Any background context you want to provide?

Is there parity with the server-side/android/iOS integration components (if applicable)?

Does this require a new integration setting? If so, please explain how the new setting works

Links to helpful docs and other external resources

@gpsamson gpsamson requested review from a team and mericsson August 8, 2019 15:18
@mericsson mericsson changed the title [DEST-877] Braze: Remove nested objects/arrays + Add undefined trait checks [DEST-877] Braze: Remove nested objects/arrays, Add undefined trait checks, use serverWorkerLocation from settings if available Aug 8, 2019
@mericsson mericsson changed the title [DEST-877] Braze: Remove nested objects/arrays, Add undefined trait checks, use serverWorkerLocation from settings if available [DEST-877] [DEST-876] Braze: Remove nested objects/arrays, Add undefined trait checks, use serverWorkerLocation from settings if available Aug 8, 2019
@mericsson mericsson merged commit abd371d into master Aug 8, 2019
@mericsson mericsson deleted the gps/braze-at branch August 8, 2019 20:51
Copy link
Contributor

@NikoRoberts NikoRoberts left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So the array issue was caught when running the tests? And the unit tests actually caught it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants