Skip to content

Conversation

@Rheed
Copy link

@Rheed Rheed commented Jan 2, 2017

Since now it didn't change if you had your toggle Off or On with false, as both options where returning null when asking for the variant value. It happens that null is not exactly the same as false, this fixes it and now properly returns a false when it's false. This problem also happened when any of your multivariant values was a false too

Hope we can fix this, as we need it for properly A/B testing 😄

@jkodumal
Copy link
Contributor

jkodumal commented Jan 2, 2017

This LGTM-- we'll do some testing on the branch via our integration harness and merge to master if it passes. Thanks for the PR!

@drichelson drichelson changed the base branch from master to Rheed/Fixing_false_value January 4, 2017 19:31
@drichelson
Copy link
Contributor

Merging into a non-master branch so we can test internally.

@drichelson drichelson merged commit 660a152 into launchdarkly:Rheed/Fixing_false_value Jan 4, 2017
@drichelson
Copy link
Contributor

Tests passed! Thanks for the PR!

@Rheed
Copy link
Author

Rheed commented Jan 5, 2017

Thanks a lot! 😉 👍

@Rheed
Copy link
Author

Rheed commented Jan 5, 2017

@drichelson hey, thanks for this, but we checked and the changes didn't get applied to the 2.0.2 version, was there a problem? 😄

@drichelson
Copy link
Contributor

Sorry about that @Rheed ! we just released 2.0.3 which contains your changes

LaunchDarklyCI pushed a commit that referenced this pull request Apr 24, 2020
ensure events aren't sent if send_events is false
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.

3 participants