All Versions
16
Latest Version
Avg Release Cycle
62 days
Latest Release
1050 days ago
Changelog History
Page 1
Changelog History
Page 1
-
v3.0.0 Changes
June 27, 2022β Added:
- β Add flag support for the client side availability property, as well as the older the ability to decode from the older clientSide format.
- π The new allFlagsState function should be used instead of allFlags if you are passing flag data to the front end for use with the JavaScript SDK. It preserves some flag metadata that the front end requires in order to send analytics events correctly. Versions 2.5.0 and above of the JavaScript SDK are able to use this metadata, but the output of allFlagsState will still work with older versions.
- π It is now possible to inject feature flags into the client from local JSON files, replacing the normal LaunchDarkly connection. This would typically be for testing purposes. See LaunchDarkly.Server.Integrations.FileData.
- β LaunchDarkly.Server.Integrations.TestData is another new way to inject feature flag data programmatically into the SDK for testingβeither with fixed values for each flag, or with targets and/or rules that can return different values for different users. Unlike FileData, this mechanism does not use any external resources, only the data that your test code has provided.
π Changed:
- π CI builds now include a cross-platform test suite implemented in https://github.com/launchdarkly/sdk-test-harness. This covers many test cases that are also implemented in unit tests, but may be extended in the future to ensure consistent behavior across SDKs in other areas.
- The SDK will track the last known server time as specified in the Date header when sending events. This value, along with the current system time, will be used to determine if debug event should still be sent.
- VariationIndex has been changed from Natural to Integer.
π Fixed:
- When evaluating against a user attribute, if the attribute is null, it should always be treated as a non-match.
-
v2.2.0 Changes
June 17, 2021β Added:
- π The SDK now supports the ability to control the proportion of traffic allocation to an experiment. This works in conjunction with a new platform feature now available to early access customers.
-
v2.1.1 Changes
March 05, 2021π Changed:
- β‘οΈ Updated dependency ranges. Thanks @dbaynard !
-
v2.1.0 Changes
February 04, 2021β Added:
- β Added the
alias
function. This can be used to associate two user objects for analytics purposes by generating an alias event.
- β Added the
-
v2.0.2 Changes
October 14, 2020[2.0.2] - 2020-10-13
π Fixed:
- β Removed unused legacy "sel" field from flag model.
-
v2.0.1 Changes
August 28, 2020 -
v2.0.0 Changes
April 22, 2020[2.0.0] - 2020-04-21
π Changed:
- β
The function
userSetKey
is now takesText
instead ofMaybe Text
for the key. This originally existed for compatibility with an internal test suite.
β Removed:
- π The constructor
EvalErrorUserNotSpecified
has been removed fromEvalErrorKind
.
- β
The function
-
v1.0.4 Changes
April 06, 2020 -
v1.0.3 Changes
March 31, 2020[1.0.3] - 2020-03-31
π Fixed:
- Standardize streaming retry behavior. Changed handling of status codes. Exponential back-off is now reset after 60 seconds of successful streaming.
-
v1.0.2 Changes
March 16, 2020[1.0.2] - 2020-03-16
π Fixed:
- β Added a timeout on SSE reads to 5 minutes.
- π Fixed an issue where reading SSE streams would burn CPU in certain edge cases