Skip to content

Conversation

mikeproeng37
Copy link
Contributor

No description provided.

@mikeproeng37
Copy link
Contributor Author

build

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 256a085 on ali/fix_event_sending_disabled_feature into c948863 on master.

Copy link
Contributor

@aliabbasrizvi aliabbasrizvi left a comment

Choose a reason for hiding this comment

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

LGTM. Can you take a look at the test and see if we can look at event content itself?


it 'should return false, if the user is bucketed into a feature experiment but the featureEnabled property is false' do
it 'should return false and send impression if the user is bucketed into a feature experiment but the featureEnabled property is false' do
allow(project_instance.event_dispatcher).to receive(:dispatch_event).with(instance_of(Optimizely::Event))
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we look at content of dispatch event itself?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I did try and it was giving me a lot of headache lol. The compat suite already checks the payload so I'd say we merge this in!

Copy link
Contributor

Choose a reason for hiding this comment

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

Go for it.

@mikeproeng37 mikeproeng37 merged commit c4e1e0b into master Jun 19, 2018
@aliabbasrizvi aliabbasrizvi changed the title Ali/fix event sending disabled feature Send impression event when variation has feature disabled Jun 19, 2018
@mikeproeng37 mikeproeng37 deleted the ali/fix_event_sending_disabled_feature branch June 27, 2018 18:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants