LaunchDarkly Client-side SDK for Flutter mobile applications
OTHER License
Bot releases are visible (Hide)
Published by LaunchDarklyReleaseBot 9 months ago
Published by LaunchDarklyReleaseBot 9 months ago
Published by LaunchDarklyReleaseBot 9 months ago
Published by tanderson-ld about 1 year ago
Published by LaunchDarklyReleaseBot about 1 year ago
Published by tanderson-ld about 1 year ago
Published by tanderson-ld over 1 year ago
Published by tanderson-ld over 1 year ago
Published by kinyoklion over 1 year ago
The latest version of this SDK supports LaunchDarkly's new custom contexts feature. Contexts are an evolution of a previously-existing concept, "users." Contexts let you create targeting rules for feature flags based on a variety of different information, including attributes pertaining to users, organizations, devices, and more. You can even combine contexts to create "multi-contexts."
For detailed information about this version, please refer to the list below. For information on how to upgrade from the previous version, please read the migration guide.
LDContext
and associated builders which define the new context model.LDUser
parameter, there is now an overload (ex: startWithContext
) that takes an LDContext
. The SDK still supports LDUser
for now, but LDContext
is the preferred model and LDUser
may be removed in a future version.secondary
attribute which existed in LDUser
is no longer a supported feature. If you set an attribute with that name in LDContext
, it will simply be a custom attribute like any other.device
and os
values to the user attributes. Applications that wish to use device/OS information in feature flag rules must explicitly add such information.maxCachedUsers
is now maxCachedContexts
LDConfig.privateAttributeNames
is now privateAttributes
secondary
meta-attribute in LDUser
and LDUser.Builder
.alias
method no longer exists because alias events are not needed in the new context model.inlineUsersInEvents
option no longer exists because it is not relevant in the new context model.Published by LaunchDarklyReleaseBot over 1 year ago
LDConfigBuilder.applicationInfo()
and .applicationVersion()
, for configuration of application metadata that may be used in LaunchDarkly analytics or other product features. This does not affect feature flag evaluations.Published by LaunchDarklyReleaseBot almost 2 years ago
Published by LaunchDarklyReleaseBot about 2 years ago
Published by LaunchDarklyReleaseBot about 2 years ago
device
and os
custom attributes would not be populated in the user object. These will now be populated correctly.Published by kinyoklion over 2 years ago
The version numbers 1.1.0 and 1.1.1 were skipped. These versions were consumed due to issues during our release process.
identify
calls were blocking and could trigger ANRs. They maintain the same interface, and can be awaited, but now they no longer block the calling thread.Published by gwhelanLD almost 3 years ago
First supported release of LaunchDarkly's Flutter SDK. This release contains no SDK code changes from the prior beta release.
Published by gwhelanLD about 3 years ago
This is a breaking beta release. The changelog may not detail all changes between beta releases. The SDK is considered to be an unsupported beta until release 1.0.0.
LDClient.startFuture
which can be used to get a Future
that completes when the SDK has received the most recent flag values for the configured user after starting.LDClient.isInitialized
which can be used to determine whether the SDK has has received the most recent flag values after starting.LDConfigBuilder.maxCachedUsers
.LDConfigBuilder
setters have had the set
prefix removed, e.g. LDConfigBuilder.setOffline
has become LDConfigBuilder.offline
.LDClient.isOnline
has been replaced with LDClient.isOffline
for consistency with other LaunchDarkly SDKs.Published by gwhelanLD about 3 years ago
This is a breaking beta release. The changelog may not detail all changes between beta releases. The SDK is considered to be an unsupported beta until release 1.0.0.
alias
method to LDClient
. 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 the identify
method; by setting autoAliasingOptOut
to true
. identify
will not automatically generate alias events.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.Published by gwhelanLD almost 4 years ago
This is the first public release of the LaunchDarkly Flutter client-side SDK. The SDK is considered to be an unsupported beta until release 1.0.0.
identify
.