Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Support Microsoft Feature Management schema for main branch #370
Support Microsoft Feature Management schema for main branch #370
Changes from 1 commit
b9b4aa2
e64f2c8
6ae3362
91385f0
353eb43
43437fe
016dbf0
ee84ec9
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Do we need to fallback for Microsoft Feature Flag schema? I don't think we would ever have it without the
feature_management
wrappers. But I suppose we could support customers who want to do that? I prefer we don't support it.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.
@jimmyca15
I am kind of convinced by Ross. I agree that we might never have it without the "feature_management" wrappers.
In the Microsoft Feature Management schema, "feature_management" is a required property. So I think we should not support fallback for it.
Previously, "FeatureFlags" array was under "FeatureManagement" section. With the complexity brought by the RootConfigurationFallBack behavior, we have to use the "EnsureInit" pattern. Now, the Microsoft Feature Management schema is under "feature_management", we can tell which schema is being used in the constructor. We can simplify the code if we don't support the RootConfigurationFallBack for Microsoft Feature Management schema.