Skip to content

Commit 8ef762a

Browse files
committed
Update feature-management-python-reference.md
1 parent 23ee461 commit 8ef762a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/azure-app-configuration/feature-management-python-reference.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -179,7 +179,7 @@ The `feature_flags` provided to `FeatureManager` can either be the `AzureAppConf
179179

180180
Creating a feature filter provides a way to enable features based on criteria that you define. To implement a feature filter, the `FeatureFilter` interface must be implemented. `FeatureFilter` has a single method named `evaluate`. When a feature specifies that it can be enabled for a feature filter, the `evaluate` method is called. If `evaluate` returns `true`, it means the feature should be enabled.
181181

182-
The following snippet demonstrates how to add a customized feature filter `MyCriteriaFilter`.
182+
The following snippet demonstrates how to add a customized feature filter `MyCustomFilter`.
183183

184184
```python
185185
feature_manager = FeatureManager(feature_flags, feature_filters=[MyCustomFilter()])
@@ -280,10 +280,10 @@ Either a user can be specified directly in the `is_enabled` call or a `Targeting
280280

281281
```python
282282
# Directly specifying the user
283-
feature_manager = FeatureManager(feature_flags, "test_user")
283+
result = is_enabled(feature_flags, "test_user")
284284

285285
# Using a TargetingContext
286-
feature_manager = FeatureManager(feature_flags, TargetingContext(user_id="test_user", groups=["Ring1"]))
286+
result = is_enabled(feature_flags, TargetingContext(user_id="test_user", groups=["Ring1"]))
287287
```
288288

289289
### Targeting exclusion

0 commit comments

Comments
 (0)