Choose bucket

[maurerbot]

Adding an optional param for the caller to choose an alternative.

Use case example:

1. Participate user in experiment A.
2. Receive bucket chosen for experiment A.
3. Participate user in subsequent experiments B, C, and D in the same bucket as A.
4. Convert each experiment individually

NOTE: this is a solution to the hash being generated by name+id rather than just id
https://github.com/seatgeek/sixpack/blob/master/sixpack/models.py#L348

[coveralls]

Coverage increased (+0.21%) to 78.7% when pulling 0c8511e on VerticodeLabs:choose-bucket into 3a185aa on seatgeek:master.

[coveralls]

Coverage increased (+0.21%) to 78.7% when pulling 8bff521 on VerticodeLabs:choose-bucket into 3a185aa on seatgeek:master.

[ahmadnassri]

👍

[brianirish]

👍

[hutchic]

👍

[hghazal]

👍

[kennethklee]

looks good 👍

[nickveenhof]

Version changes should not be addressed in a PR. See the README in the main repository folder.

[nickveenhof]

I am not sure what the usecase is here. Are you not able to create a new experiment or change the client_id on the implementation side so that it always is unique? I'd love for this patch to see more documentation and its impact.

[maurerbot]

@nickveenhof I forgot what the use case was now but from what I do remember if you have 1+n tests and you wanted to participate the user in test n based on the bucked chosen from test 1. Another case was to use sixpack to follow a users state conversion.

e.g.

A user can be move to several states (a -> b -> c -> d and a -> b -> c -> a) over time and you want to see if the convert overtime so if they are in state b you participate them in c, d, and a and convert them when the move to those states.