-
Notifications
You must be signed in to change notification settings - Fork 20
Feature Flag & Roll out models #25
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
Feature Flag & Roll out models #25
Conversation
Datafile parsing & Validation Travis Issue fixed (mono specific version for unit testing)
Can one of the admins verify this patch? |
@asaschachar Can you please assign reviewer. JIRA tickets OASIS-1942 and OASIS-1943 are covered. OASIS-1948 and OASIS-1949 are covered. |
@@ -51,7 +51,7 @@ public void Setup() | |||
public void TestInit() | |||
{ | |||
// Check Version | |||
Assert.AreEqual(2, Config.Version); |
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.
Until we GA feature flags, we need to support BOTH datafile v2 and datafile v4.
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.
Nah because we can keep this in the master branch and deploy from the 1.2.x branch of we need to do so before FF GA.
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.
Mostly looks good. Please address the two issues mentioned
|
||
namespace OptimizelySDK.Entity | ||
{ | ||
public class FeatureVariableUsage : IdKeyEntity |
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.
This should have a value
prop
|
||
// Check Variation ID Map | ||
var variationIdMap = new Dictionary<string, object> | ||
var expectedVariationIdMap = new Dictionary<string, object> |
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.
Can you generate some variable usages within variations of one of the experiment and assert that the FeatureVariableUsageInstance
maps are generated properly for those variations.
@mikeng13 Thanks for pointing out variable usage test case, it was the issue in the SDK, was not deserializing variables in variation. Fixed it here. |
@msohailhussain I ran our E2E test suite and the testapp build failed with this error:
|
@mikeng13 sorry about it, let me investigate. |
@mikeng13 Fixed it, We manually add files in .netstandard project, and it missed 'closed' markup. |
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. E2E tests all pass except for one known failing test.
Feature Notification Center
* Feature Notification Center (#25) * Added FeatureExperiment and FeatureRollout notification types. * Fixed code review defects. * TestBucketLogsCorrectlyWhenUserProfileFailsToSave fixed. Added one more test case for FeatureRollout Notification type. Removed ConfigParser method which was not being used. * remvoed feature experiment and featurue rollout notifications. * removed feature experiment and feature rollback callbacks. * fixed unit test issue.
Datafile parsing & Validation
Travis Issue fixed (set mono specific version for unit testing)