Skip to content

Conversation

mjc1283
Copy link
Contributor

@mjc1283 mjc1283 commented Sep 21, 2018

Summary

With this change, attribute properties with null or undefined values are filtered out of impression events that are sent as a result of a feature being enabled via a feature test. This makes isFeatureEnabled behave the same way as activate with respect to null/undefined values in attributes in impression events.

Test plan

Added new unit test

@coveralls
Copy link

Coverage Status

Coverage increased (+0.6%) to 97.691% when pulling 0d0667e on mcarroll/is-feature-enabled-filter-empty-attributes into feb34eb on master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage increased (+0.6%) to 97.691% when pulling 0d0667e on mcarroll/is-feature-enabled-filter-empty-attributes into feb34eb on master.

Copy link
Contributor

@mikeproeng37 mikeproeng37 left a comment

Choose a reason for hiding this comment

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

Thanks for fixing! Lgtm

@msohailhussain
Copy link
Contributor

@mikeng13 @aliabbasrizvi
I assume the right place to filter attributes is in eventbuilder which is done in this PR.
#166

@mjc1283
Copy link
Contributor Author

mjc1283 commented Sep 21, 2018

I think @msohailhussain is right - that's the best place to fix this.

@mjc1283 mjc1283 closed this Sep 21, 2018
@mjc1283 mjc1283 deleted the mcarroll/is-feature-enabled-filter-empty-attributes branch September 27, 2018 00:56
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.

5 participants