Source code | Package (npm) | Samples

• Fixed a bug where isEnabled returned false when an unregistered feature filter was encountered while using RequirementType Any, even if other registered filters in the list could enable the feature. #158

• Upgraded various dependencies. #150

• Exported IFeatureFilterEvaluationContext so that custom IFeatureFilter implementations can use proper type information for the evaluateAsync context parameter. #135

• Added a Recurrence option to the TimeWindowFilter to support recurring time window. This enables scenarios where a feature flag is activated based on a recurrence pattern, such as every day after 5 PM or every Friday. See the Enable features on a schedule for more details.

• Stablized the targeting context accessor. You can configure an ITargetingContextAccessor when initializing the FeatureManager through FeatureManagerOptions.targetingContextAccessor. #93

• Stablized the feature evaluation event properties which include: "Version", "FeatureName", "Enabled", "TargetingId", "Variant", "VariantAssignmentReason", "DefaultWhenEnabled" and "VariantAssignmentPercentage".

• Introduced ITargetingContextAccessor to allow FeatureManager to get ambient targeting context in the server scenario. You can configure a targeting context accessor when initializing the FeatureManager through FeatureManagerOptions.targetingContextAccessor. #93

This is the first stable release of the following features.

• Variant Feature Flags

  A variant feature flag is an enhanced feature flag that supports multiple states or variations. While it can still be toggled on or off, it also allows for different configurations, ranging from simple primitives to complex JSON objects. Variant feature flags are particularly useful for feature rollouts, configuration rollouts, and feature experimentation (also known as A/B testing).

  The new getVariant method of FeatureManager has been introduced to evaluate the assigned variant based on the variant feature flag configuration and targeting context. #13

• Feature Evaluation Telemetry

  Telemetry provides observability into flag evaluations, offering insights into which users received specific flag results. This enables more powerful metric analysis, such as experimentation.

  The new onFeatureEvaluated property of FeatureManagerOptions allows you to set a custom callback for all feature evaluations. This hook can be used to publish telemetry. You can call createTelemetryPublisher API from @microsoft/feature-management-applicationinsights-browser and @microsoft/feature-management-applicationinsights-node packages to publish feature evaluation event to Application Insights. #36

• Fixed a bug that caused error when calling getFeatureFlags and listFeatureNames. #74

• Added validation for feature flag properties. #17

• No changes in this release.

• Added support for variant feature flags. A variant feature flag is an enhanced feature flag that supports multiple states or variations. While it can still be toggled on or off, it also allows for different configurations, ranging from simple primitives to complex JSON objects. Variant feature flags are particularly useful for feature rollouts, configuration rollouts, and feature experimentation (also known as A/B testing). #13

• Added support for telemetry in feature flags. Telemetry is a powerful feature that allows you to track how your feature flags are being used. It provides insights into the effectiveness of your feature flags and helps you make data-driven decisions. Telemetry is particularly useful for feature experimentation (also known as A/B testing) and feature rollouts. #36

This is the first stable release of the following features.

• Loading of feature flags from object and map.
• Feature flag evaluation with ambient context or user-provided context.
• Built-in feature filters Microsoft.TimeWindow and Microsoft.Targeting.

Added support for the following features.

• Loading of feature flags from object and map.
• Feature flag status evaluation with or without context.
• Feature filters including built-in filters Microsoft.TimeWindow and Microsoft.Targeting.