Release 2.3.0-beta

[2.3.0-beta] - August 27th, 2020

Upgrade @optimizely/optimizely-sdk to 4.2.1

New Features

• useExperiment and useFeature hooks re-render when override user ID or attributes change(#64)

Bug fixes

• useExperiment and useFeature hooks return up-to-date decision values on the first call after the client is ready (#64)

Release 2.2.0

[2.2.0] - July 31st, 2020

Upgrade @optimizely/optimizely-sdk to 4.2.0

New Features

• Better offline support in React Native apps:
  • Persist downloaded datafiles in local storage for use in subsequent SDK initializations
  • Persist pending impression & conversion events in local storage

Bug fixes

• Fixed log messages for Targeted Rollouts

Release 2.1.0

[2.1.0] - July 8th, 2020

Upgrade @optimizely/optimizely-sdk to 4.1.0. See @optimizely/optimizely-sdk Release 4.1.0 for more details.

New Features

• Add support for JSON feature variables (#53)

Release 2.0.1

[2.0.1] - May 22nd, 2020

Bug Fixes

• Export useExperiment hook from this package (#50)

Release 2.0.0

[2.0.0] - April 30th, 2020

Upgrade @optimizely/optimizely-sdk to 4.0.0. See @optimizely/optimizely-sdk Release 4.0.0 for more details.

Breaking Changes

• Changed supported React version to 16.8+

• @optimizely/optimizely-sdk no longer adds Promise polyfill in its browser entry point

• Dropped support for Node.js version <8

New Features

• Refactored <OptimizelyFeature> to a functional component that uses the useFeature hook under the hood. See #32 for more details.

• Refactored <OptimizelyExperiment> to a functional component that uses the useExperiment hook under the hood. See #36 for more details.

• Added useExperiment hook

  • Can be used to retrieve the variation for an experiment. See #36 for more details.

• Added useFeature hook

  • Can be used to retrieve the status of a feature flag and its variables. See #28 for more details.

• Removed lodash dependency

Enhancements

• Exposed the entire context object used by <OptimizelyProvider>.
  • Enables support for using APIs which require passing reference to a context object, like useContext. #27 for more details.

Release 2.0.0-rc.2

[2.0.0-rc.2] - April 24th, 2020

Bug Fixes

• Upgrade @optimizely/optimizely-sdk to 4.0.0-rc.2. Allow creating multiple instances from the same datafile object. See @optimizely/optimizely-sdk Release 4.0.0-rc.2 for more details.

Release 2.0.0-alpha.2

[2.0.0-alpha.2] - April 3rd, 2020

Breaking Changes

• Upgrade @optimizely/optimizely-sdk to 4.0.0-alpha.1. Promise polyfill no longer included. See @optimizely/optimizely-sdk Release 4.0.0-alpha.1 for more details.

Release 2.0.0-alpha.1

[2.0.0-alpha.1] - March 18th, 2020

Breaking Changes

• Changed supported React version to 16.8+

New Features

• Refactored <OptimizelyFeature> to a functional component that uses the useFeature hook under the hood. See #32 for more details.

• Refactored <OptimizelyExperiment> to a functional component that uses the useExperiment hook under the hood. See #36 for more details.

• Added useExperiment hook

  • Can be used to retrieve the variation for an experiment. See #36 for more details.

• Added useFeature hook

  • Can be used to retrieve the status of a feature flag and its variables. See #28 for more details.

Enhancements

• Exposed the entire context object used by <OptimizelyProvider>.
  • Enables support for using APIs which require passing reference to a context object, like useContext. #27 for more details.

Release 1.2.0-alpha.1

[1.2.0-alpha.1] - March 5th, 2020

New Features

• Updated minor version of core SDK (@optimizely/optimizely-sdk) dependency which, for unrecognized events sent via .track(), will impact the log levels in this SDK as well.

Release 1.1.0

[1.1.0] - January 30th, 2020

New Features

• Added a new API to get project configuration static data.
  • Call getOptimizelyConfig() to get a snapshot of project configuration static data.
  • It returns an OptimizelyConfig instance which includes a datafile revision number, all experiments, and feature flags mapped by their key values.
  • Added caching for getOptimizelyConfig - OptimizelyConfig object will be cached and reused for the lifetime of the datafile.
  • For details, refer to our documentation page: https://docs.developers.optimizely.com/full-stack/docs/optimizelyconfig-react.