2.0.5

chore(release): 2.0.5 (#125)

* Fix(nodejs/event_dispatcher): update error/resp handlers (#123)

- (nodejs) Prevent crash when `http`/`https` emits an error by adding an 'error' listener
- (nodejs) Fix `requestCallback` to conform to its role as a 'response' listener; notably, ensure it is called when the first argument is interpeted as the `http.IncomingMessage`, and _not_ called in the event of an error (as expected by `Optimizely#_sendImpressionEvent`/`Optimizely#track`).

Tested that this version (as 2.1.2-0) _does_ emit the messages expected in the demo app.

Fixes #122
Fixes #124

2.1.1

chore: 2.1.1 release (#118)

* Fix impression sent from feature experiment variation toggled off. (#117)

2.0.4

chore: release 2.0.4 (#119)

* Fix impression sent from feature experiment variation toggled off. (#117)

2.1.0

• Introduces support for bot filtering. (#99)

2.0.3

• Remove request dependency (#98)
• Add package-lock.json (#100)
• Input validation in Activate, Track, and GetVariation methods (#91 by @mfahadahmed)

Release 2.0.1

April 16th, 2018

• Improve browser entry point by pointing to the browser index file instead of the webpack-compiled bundle. (@DullReferenceException in #88)

Release 2.0.0

April 11th, 2018

This major release of the Optimizely SDK introduces APIs for Feature Management. It also introduces some breaking changes listed below.

New Features

• Introduces the isFeatureEnabled API to determine whether to show a feature to a user or not.

var enabled = optimizelyClient.isFeatureEnabled('my_feature_key', 'user_1', userAttributes);

• You can also get all the enabled features for the user by calling the following method which returns a list of strings representing the feature keys:

var enabledFeatures = optimizelyClient.getEnabledFeatures('user_1', userAttributes);

• Introduces Feature Variables to configure or parameterize your feature. There are four variable types: Integer, String, Double, Boolean.

var stringVariable = optimizelyClient.getFeatureVariableString('my_feature_key', 'string_variable_key', 'user_1');
var integerVariable = optimizelyClient.getFeatureVariableInteger('my_feature_key', 'integer_variable_key', 'user_1');
var doubleVariable = optimizelyClient.getFeatureVariableDouble('my_feature_key', 'double_variable_key', 'user_1');
var booleanVariable = optimizelyClient.getFeatureVariableBoolean('my_feature_key', 'boolean_variable_key', 'user_1');

Breaking changes

• The track API with revenue value as a stand-alone parameter has been removed. The revenue value should be passed in as an entry of the event tags map. The key for the revenue tag is revenue and will be treated by Optimizely as the key for analyzing revenue data in results.

var eventTags = {
  'revenue': 1200
};

optimizelyClient.track('event_key', 'user_id', userAttributes, eventTags);

• The package name has changed from optimizely-client-sdk to optimizely-sdk as we have consolidated both Node and JavaScript SDKs into one.

Release 2.0.0-beta1

March 29th, 2018

This major release of the Optimizely SDK introduces APIs for Feature Management. It also introduces some breaking changes listed below.

New Features

• Introduces the isFeatureEnabled API to determine whether to show a feature to a user or not.

var enabled = optimizelyClient.isFeatureEnabled('my_feature_key', 'user_1', userAttributes);

• You can also get all the enabled features for the user by calling the following method which returns a list of strings representing the feature keys:

var enabledFeatures = optimizelyClient.getEnabledFeatures('user_1', userAttributes);

• Introduces Feature Variables to configure or parameterize your feature. There are four variable types: Integer, String, Double, Boolean.

var stringVariable = optimizelyClient.getFeatureVariableString('my_feature_key', 'string_variable_key', 'user_1');
var integerVariable = optimizelyClient.getFeatureVariableInteger('my_feature_key', 'integer_variable_key', 'user_1');
var doubleVariable = optimizelyClient.getFeatureVariableDouble('my_feature_key', 'double_variable_key', 'user_1');
var booleanVariable = optimizelyClient.getFeatureVariableBoolean('my_feature_key', 'boolean_variable_key', 'user_1');

Breaking changes

• The track API with revenue value as a stand-alone parameter has been removed. The revenue value should be passed in as an entry of the event tags map. The key for the revenue tag is revenue and will be treated by Optimizely as the key for analyzing revenue data in results.

var eventTags = {
  'revenue': 1200
};

optimizelyClient.track('event_key', 'user_id', userAttributes, eventTags);

• The package name has changed from optimizely-client-sdk to optimizely-sdk as we have consolidated both Node and JavaScript SDKs into one.

Release 1.6.0

• Bump optimizely-server-sdk to version 1.5.0, which includes:
  • Implemented IP anonymization.
  • Implemented bucketing IDs.
  • Implemented notification listeners.

Release 1.5.1

• Bump optimizely-server-sdk to version 1.4.2, which includes:
  • Bug fix to filter out undefined values in attributes and event tags
  • Remove a duplicated test