Skip to content

Conversation

msohailhussain
Copy link
Contributor

Datafile parsing & Validation
Travis Issue fixed (set mono specific version for unit testing)

Datafile parsing & Validation
Travis Issue fixed (mono specific version for unit testing)
@optibot
Copy link
Contributor

optibot commented Oct 20, 2017

Can one of the admins verify this patch?

@msohailhussain
Copy link
Contributor Author

@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);

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.

Copy link
Contributor

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.

Copy link
Contributor

@mikeproeng37 mikeproeng37 left a 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
Copy link
Contributor

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>
Copy link
Contributor

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.

@msohailhussain
Copy link
Contributor Author

@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.
7fa0f9a

@mikeproeng37
Copy link
Contributor

@msohailhussain I ran our E2E test suite and the testapp build failed with this error:

/optimizelysdk/sdk/OptimizelySDK.NetStandard16/OptimizelySDK.NetStandard16.csproj(54,7): error MSB4025: The project file could not be loaded. The 'Compile' start tag on line 23 position 4 does not match the end tag of 'ItemGroup'. Line 54, position 7.

Build FAILED.

/optimizelysdk/sdk/OptimizelySDK.NetStandard16/OptimizelySDK.NetStandard16.csproj(54,7): error MSB4025: The project file could not be loaded. The 'Compile' start tag on line 23 position 4 does not match the end tag of 'ItemGroup'. Line 54, position 7.
/optimizelysdk/sdk/OptimizelySDK.NetStandard16/OptimizelySDK.NetStandard16.csproj(54,7): error MSB4025: The project file could not be loaded. The 'Compile' start tag on line 23 position 4 does not match the end tag of 'ItemGroup'. Line 54, position 7.
    0 Warning(s)
    2 Error(s)```

@msohailhussain
Copy link
Contributor Author

@mikeng13 sorry about it, let me investigate.

@msohailhussain
Copy link
Contributor Author

@mikeng13 Fixed it, We manually add files in .netstandard project, and it missed 'closed' markup.

Copy link
Contributor

@mikeproeng37 mikeproeng37 left a 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.

@mikeproeng37 mikeproeng37 merged commit 86c8026 into optimizely:master Oct 25, 2017
kellyroach-optimizely pushed a commit that referenced this pull request Nov 17, 2017
Feature Notification Center
thomaszurkan-optimizely pushed a commit that referenced this pull request Nov 27, 2017
* 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.
@mfahadahmed mfahadahmed deleted the featureflag_model_parsing branch March 7, 2018 07:27
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.

5 participants