Skip to content

Releases: launchdarkly/react-client-sdk

2.22.2

07 Apr 00:52
Compare
Choose a tag to compare

[2.22.2] - 2021-04-06

Changed:

  • Updated the SDK's peer dependencies so that it can run in an application with React 17 (thanks, maclockard!)

2.22.1

03 Apr 01:44
Compare
Choose a tag to compare

[2.22.1] - 2021-04-02

Fixed:

  • The property LDOptions.inlineUsersInEvents was not included in the TypeScript definitions for the JavaScript SDK.

2.22.0

27 Jan 20:42
Compare
Choose a tag to compare

[2.22.0] - 2021-01-27

Added:

  • Added the alias method to LDClient. This method can be used to associate two user objects for analytics purposes. When invoked, this method will queue a new alias event to be sent to LaunchDarkly.
  • Added the autoAliasingOptOut configuration option. This can be used to control the new automatic aliasing behavior of the identify method; by passing autoAliasingOptOut: true, identify will not automatically generate alias events.

Changed:

  • LDClient's identify method will now automatically generate an alias event when switching from an anonymous to a known user. This event associates the two users for analytics purposes as they most likely represent a single person.

2.21.0

17 Nov 20:25
Compare
Choose a tag to compare

[2.21.0] - 2020-11-17

Fixed:

  • The camelCaseKeys utility function is now exported as a function instead of as an object containing a camelCaseKeys function. camelCaseKeys.camelCaseKeys remains for backwards compatibility.
  • Updated the LDEvaluationDetail.reason type definition to be nullable. This value will be null when LDOptions.evaluationReasons is false.

Deprecated:

  • camelCaseKeys.camelCaseKeys is now deprecated-- see the note above.

2.20.2

14 Sep 23:35
Compare
Choose a tag to compare

[2.20.2] - 2020-09-14

Fixed:

  • In streaming mode, when connecting to the Relay Proxy rather than directly to the LaunchDarkly streaming service, if the current user was changed twice within a short time it was possible for the SDK to revert to flag values from the previous user. (Fixed in JS SDK 2.18.1)

2.20.1

19 Aug 23:05
Compare
Choose a tag to compare

[2.20.1] - 2020-08-19

Fixed:

  • Fixed an issue where change listeners would update the component state when any flag was modified, even if the client instance was configured such that it was not subscribed for the modified flag. (Thanks, clayembry!)

2.20.0

17 Jul 18:07
Compare
Choose a tag to compare

[2.20.0] - 2020-07-17

Changed:

2.19.0

15 Jul 23:06
Compare
Choose a tag to compare

[2.19.0] - 2020-07-15

Added:

  • Exposed LDProvider as a standalone component. (Thanks, nimi and morton!)
  • A new configuration option, deferInitialization, allows LDClient initialization to be deferred until the user object is defined. (Thanks, bezreyhan!)

Fixed:

  • Removed uses of String.startsWith that caused errors in Internet Explorer unless a polyfill for that function was present.

2.18.2

27 May 20:15
Compare
Choose a tag to compare

[2.18.2] - 2020-05-27

Fixed:

  • Fixed a TypeError where TypeScript attempted to redefine the default property on withLDProvider. This issue was introduced in version 2.18.1 of this SDK. (#36)

2.18.1

19 May 22:14
Compare
Choose a tag to compare

[2.18.1] - 2020-05-19

Fixed:

  • Updated JS SDK version to 2.17.5, to pick up bug fixes in 2.17.5, 2.17.4, 2.17.3, 2.17.2, and 2.17.1. The intended practice is to release a new React SDK patch every time there is a JS SDK patch (unless several JS SDK patches are released very close together), but this had fallen behind.