Releases: launchdarkly/js-sdk-common
Releases · launchdarkly/js-sdk-common
3.5.0
[3.5.0] - 2022-01-14
Added:
- New configurable logger factory
commonBasicLogger
andBasicLoggerOptions
. ThecommonBasicLogger
method is not intended to be exported directly in the SDKs, but wrapped to provide platform-specific behavior.
Fixed:
- Any exceptions thrown by the platform-specific local storage implementation (for instance, if we are in a browser and
window.localstorage
is available but disabled) are now consistently caught, and will only be logged the first time to avoid repetitive logging.
3.4.0
[3.4.0] - 2021-10-15
Added:
- Added LDOptionsBase.requestHeaderTransform allowing custom headers to be added to all requests.
3.3.4
[3.3.4] - 2021-10-15
Fixed:
- Reverted change to
uuid
dependency while working on some compatibility issues.
3.3.3
3.3.2
[3.3.2] - 2021-06-07
Fixed:
- Events for the LaunchDarkly debugger are now properly pre-processed to omit private user attributes, as well as enforce only expected top level attributes are sent.
- Events for the LaunchDarkly debugger now include the index of the variation responsible for the evaluation result.
3.3.1
[3.3.1] - 2021-04-01
Fixed:
- The property
LDOptionsBase.inlineUsersInEvents
was not included in the TypeScript definitions. - Fixed an outdated documentation link (thanks, sinchang!)
- Fixed a documentation typo (thanks, Doesntmeananything!)
3.3.0
[3.3.0] - 2021-01-26
Added:
- Added the
alias
method. 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 theidentify
method; by passingautoAliasingOptOut: true
,identify
will not automatically generate alias events.
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.
3.2.12
[3.2.12] - 2021-01-25
Changed:
- When creating a stream connection, we now set a
streamReadTimeoutMillis
option which is hard-coded to the standard LaunchDarkly stream timeout of 5 minutes. This option is implemented bylaunchdarkly-eventsource
1.4.0 and higher, and should be ignored by SDKs that are not using that EventSource implementation.
3.2.11
[3.2.11] - 2020-11-17
Fixed:
- Updated the
LDEvaluationDetail.reason
type definition to be nullable. This value will benull
whenLDOptions.evaluationReasons
isfalse
.
3.2.10
[3.2.10] - 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.