-
Notifications
You must be signed in to change notification settings - Fork 36
Add forced-decisions APIs to OptimizelyUserContext #361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some early comments :)
Co-authored-by: ozayr-zaviar <[email protected]>
Co-authored-by: ozayr-zaviar <[email protected]>
Co-authored-by: ozayr-zaviar <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rest of the comments, @mnoman09 will verify.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
few more comments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested some changes.
@msohailhussain @mnoman09 I consolidated the functions into one. Here: python-sdk/optimizely/project_config.py Lines 668 to 700 in ab40d9e
When you review this pls look carefully. The two functions I consolidated were each called on a different object: get_flag_variation_by_id() was called on project_config. ----> in user_event_factory.py So I made a little change in find_validated_forced_decision() here, so the single function is only called on project_config: https://github.com/optimizely/python-sdk/pull/361/files#diff-4df94492754236d1784d8b2987b84acd6af0ea3d97a0a2e54e61fb3f03acb04cR265-R268 unit tests and FSC tests pass. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few changes suggested
* project config refactor * use existing loop to generate flag_variation_map * get_variation_from_experiment_rule and get_variation_from_delivery_rule removed * fsc test fix * comment addressed * commented code removed * comments from main forced decision PR resolved Co-authored-by: ozayr-zaviar <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All look good except for a small change suggested!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
@msohailhussain @mnoman09 @yasirfolio3 Can you please approve this PR so I can merge it? (mark requested changes as resolved) TY |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
already approved by 2 devx members.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm on behalf of yasir and noman.
Summary
Add a set of new APIs for forced-decisions to OptimizelyUserContext:
Test plan
Issues