prepare 3.3.0 release #198
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Conflicts: # launchdarkly-android-client/src/main/java/com/launchdarkly/android/LDClient.java
…or null for variations.
…rializer/deserializers to classes in gson package and create one for PUT responses. Removed BaseUserSharedPreferences.
…s to synchronize to prevent data race on sending, updating, and clearing event store. Move SummaryEventSharedPreferences and UserSummaryEventSharedPreferences out of response package.
…rence. Fix various warnings.
…in SharedPrefsFlagStore.
# Conflicts: # launchdarkly-android-client/src/main/java/com/launchdarkly/android/LDClient.java
adapter." Wrong branch... This reverts commit 69c1c9b.
* Changed shared preferences store system to user a single FlagStore system that holds all the information on a flag to prevent issues arising from unsynchronized separate stores for flag meta-data and values. * Abstract FlagStoreManager from FlagStore, new FlagStoreFactory class so manager can construct FlagStores of unknown type. Reformatted interfaces. Removed unused imports. * Handle null case in allFlags, actually commit changes to UserManager. * Hopefully fix edge cases in summary event reporting to pass testing. * Hopefully fix edge cases in summary event reporting to pass testing. * Simplify getFeaturesJsonObject as no longer using -1 as placeholder for null for variations. * Make Flag non-mutable. Move GsonCache to gson package, move custom serializer/deserializers to classes in gson package and create one for PUT responses. Removed BaseUserSharedPreferences. * Send summary event even if stored flag doesn't exist. * Move sendSummaryEvent update code to UserSummaryEventSharedPreferences to synchronize to prevent data race on sending, updating, and clearing event store. Move SummaryEventSharedPreferences and UserSummaryEventSharedPreferences out of response package. * Update SharedPrefsFlagStore to hold StoreUpdatedListener in weak reference. Fix various warnings. * Migration code for upcoming flagstore. * Remove couple of debug messages. * Handle todos. * Revert to old String behavior for allFlags, initialize WeakReference in SharedPrefsFlagStore. * Better implementation of EvaluationReason serialization type adapter. * Remove isUnknown argument from SummaryEventSharedPreferences methods. Use Runnable instead of Callable in UserManager to avoid useless return nulls. Rename FlagStoreFactoryInterface to FlagStoreFactory. * Statically initialize Gson instance in GsonCache. * Make Gson instance in GsonCache final on principle.
# Conflicts: # launchdarkly-android-client/src/main/java/com/launchdarkly/android/LDClient.java # launchdarkly-android-client/src/main/java/com/launchdarkly/android/SummaryEventSharedPreferences.java # launchdarkly-android-client/src/main/java/com/launchdarkly/android/UserManager.java # launchdarkly-android-client/src/main/java/com/launchdarkly/android/UserSummaryEventSharedPreferences.java # launchdarkly-android-client/src/main/java/com/launchdarkly/android/flagstore/sharedprefs/SharedPrefsFlagStoreFactory.java # launchdarkly-android-client/src/main/java/com/launchdarkly/android/flagstore/sharedprefs/SharedPrefsFlagStoreManager.java # launchdarkly-android-client/src/main/java/com/launchdarkly/android/gson/EvaluationReasonSerialization.java # launchdarkly-android-client/src/main/java/com/launchdarkly/android/gson/GsonCache.java
add methods to get value with explanation; refactor existing variation methods
fix/expand doc comments for public methods
add version string getter method
…ata-source-config # Conflicts: # launchdarkly-android-client-sdk/src/androidTest/java/com/launchdarkly/sdk/android/DiagnosticEventTest.java
…-config # Conflicts: # launchdarkly-android-client-sdk/src/androidTest/java/com/launchdarkly/sdk/android/DiagnosticEventTest.java
…ata-source-config
…-config # Conflicts: # launchdarkly-android-client-sdk/src/main/java/com/launchdarkly/sdk/android/LDClient.java
…erformance issue) (#279) * don't keep summary event counters in SharedPreferences * don't create a summary event if there's no data
…ata-source-config
…builder (non-U2C, for 3.x) add sub-configuration builder for events
…nfig (non-U2C, for 3.x) add configuration builders for polling/streaming
(non-U2C, for 3.x) add configuration builder for HTTP
(non-U2C, for 3.x) add configuration builder for service endpoints
louis-launchdarkly
approved these changes
Dec 2, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[3.3.0] - 2022-12-02
The primary purpose of this release is to introduce newer APIs for SDK configuration, corresponding to how configuration will work in the upcoming 4.0 release. The corresponding older APIs are now deprecated; switching from them to the newer ones now will facilitate migrating to 4.0 in the future. This also brings the Android SDK's API closer in line with other current LaunchDarkly SDKs, such as the Java SDK and the .NET SDKs.
Previously, most configuration options were set by setter methods in
LDConfig.Builder. These are being superseded by builders that are specific to one area of functionality: for instance,Components.streamingDataSource()andComponents.pollingDataSource()provide builders/factories that have options specific to streaming or polling, and the SDK's many options related to analytics events are now in a builder returned byComponents.sendEvents(). Using this newer API makes it clearer which options are for what, and makes it impossible to write contradictory configurations like.stream(true).pollingIntervalMillis(30000).The new configuration builders also include some options for SDK behavior that could not previously be configured; see "Added".
Added:
Components, containing factory methods for the various configuration builders.com.launchdarkly.sdk.android.integrations:StreamingDataSourceBuilder,PollingDataSourceBuilder,EventProcessorBuilder,HttpConfigurationBuilder,ServiceEndpointsBuilder.LDConfig.Builder.events()toComponents.noEvents().com.launchdarkly.sdk.android.subsystems.EventProcessor.StreamingDataSourceBuilder.initialReconnectDelayMillis().Deprecated:
(all in
LDConfig.Builder)pollingIntervalMillis,stream: seePollingDataSourceBuilder.backgroundPollingIntervalMillis: seePollingDataSourceBuilderandStreamingDataSourceBuilder.allAttributesPrivate,diagnosticRecordingIntervalMillis,eventsCapacity,eventsFlushIntervalMillis,inlineUsersInEvents,privateAttributes: seeEventProcessorBuilder.connectionTimeoutMillis,headerTransform,useReport,wrapperName,wrapperVersion: seeHttpConfigurationBuilder.streamUri,pollUri,eventsUri: SeeServiceEndpointsBuilder.