Skip to content
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

Release note for JS FM v2 #1008

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions releaseNotes/JavaScriptFeatureManagement.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,28 @@

[Source code][source_code] | [Package (npm)][package] | [Samples][samples]

## 2.0.0 - Jan 14, 2025

### Enhancements

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).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a PR or issue to link to that describes this addition?


The new `getVariant` API has been introduced to evaluate the assigned variant based on the variant feature flag configuration and targeting context.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

getVariant is a function calling it API seems overly generic.

Also, this is a method on a FeatureManager type right? It would be good to fully qualify it in that case.


* __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` constructor parameter of `FeatureManager` 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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there an issue or PR this can link to?


### Bug Fix
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Bug Fix
### Bug Fixes


* Fixed a bug that caused error when calling `getFeatureFlags` and `listFeatureNames`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR or issue link?


## 2.0.0-preview.3 - Oct 24, 2024

### Enhancements
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,16 @@

[Source code][source_code] | [Package (npm)][package] | [Samples][samples]

## 2.0.0 - Jan 14, 2025

### Enhancements

This is the first stable release of the following features.

* `createTelemetryPublisher` API that enables feature evaluation telemetry to be published to Application Insights.
Copy link
Member

@jimmyca15 jimmyca15 Jan 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* `createTelemetryPublisher` API that enables feature evaluation telemetry to be published to Application Insights.
* A `createTelemetryPublisher` function has been added that enables feature evaluation telemetry to be published to Application Insights.


* `TrackEvent` API that allows users to replace existing Application Insights TrackEvent calls to include targeting information in custom events sent to Application Insights.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* `TrackEvent` API that allows users to replace existing Application Insights TrackEvent calls to include targeting information in custom events sent to Application Insights.
* A `TrackEvent` function has been added to enable sending custom events embedded with targeting information to Application Insights. This function is meant to be used in place of the Application Insights package's standard TrackEvent call.


## 2.0.0-preview.3 - Nov 8, 2024

* Updated `@microsoft/feature-management` dependency to `2.0.0-preview.3`. See the [release notes](./JavaScriptFeatureManagement.md) for more information on the changes.
Expand Down
10 changes: 10 additions & 0 deletions releaseNotes/JavaScriptFeatureManagementApplicationInsightsNode.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,16 @@

[Source code][source_code] | [Package (npm)][package] | [Samples][samples]

## 2.0.0 - Jan 14, 2025

### Enhancements

This is the first stable release of the following features.

* `createTelemetryPublisher` API that enables feature evaluation telemetry to be published to Application Insights.

* `TrackEvent` API that allows users to replace existing Application Insights TrackEvent calls to include targeting information in custom events sent to Application Insights.

## 2.0.0-preview.3 - Nov 8, 2024

### Enhancements
Expand Down
Loading