Added the alias method to LDClient. This can be used to associate two user objects for analytics purposes with an alias event.
Added the autoAliasingOptOut configuration option. This can be used to control the new automatic aliasing behavior of the identify method; by setting autoAliasingOptOut to true, identify will not automatically generate alias events.
Added the isInitialized property to LDClient. Unless the client has been set offline, this property's value is false until the client receives an initial set of flag values from the LaunchDarkly service. If the client is offline, the value will be true after initialization.
Changed
The 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.
Fixed
Some users reported synchronization issues with the internal DiagnosticReporter implementation, which has been reworked to address these issues. Thanks to @provanandparanjape for one such report (#238).
[5.4.0] - 2021-02-26
Added
alias
method toLDClient
. This can be used to associate two user objects for analytics purposes with an alias event.autoAliasingOptOut
configuration option. This can be used to control the new automatic aliasing behavior of theidentify
method; by settingautoAliasingOptOut
to true,identify
will not automatically generate alias events.isInitialized
property toLDClient
. Unless the client has been set offline, this property's value isfalse
until the client receives an initial set of flag values from the LaunchDarkly service. If the client is offline, the value will betrue
after initialization.Changed
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.Fixed
DiagnosticReporter
implementation, which has been reworked to address these issues. Thanks to @provanandparanjape for one such report (#238).