Add the capability to prevent features with feature filters from being evaluated. #143
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.
This PR adds an enhancement to define features with feature filters that should not be evaluated.
There are times when developers configure feature filters for a feature but they do not want this feature to be on. This could be pre-emptive configuration of a feature to include feature filters that is later turned on. Or it could be that a feature is frequently turned off/on but there is a desire to preserve the configuration of filters.
Here is an example feature that has a feature filter registered, but should not be evaluated.
For this feature,
await IsEnabledAsync("NonEvaluatedFeature")will returnfalse.