prepare 4.8.1 release #173
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
…2124/filter-client-side-flags # Conflicts: # src/main/java/com/launchdarkly/client/LDClientInterface.java
…ithout-reasons add new version of allFlags() that captures more metadata
add error explanation and logging for malformed flags
…e-flags add ability to filter for only client-side flags
# Conflicts: # gradle.properties # src/main/java/com/launchdarkly/client/FeatureFlag.java # src/main/java/com/launchdarkly/client/LDClient.java # src/test/java/com/launchdarkly/client/LDClientEvaluationTest.java # src/test/java/com/launchdarkly/client/LDClientOfflineTest.java
# Conflicts: # src/main/java/com/launchdarkly/client/FeatureFlagsState.java # src/main/java/com/launchdarkly/client/FlagsStateOption.java # src/main/java/com/launchdarkly/client/LDClient.java # src/main/java/com/launchdarkly/client/LDClientInterface.java # src/test/java/com/launchdarkly/client/FeatureFlagsStateTest.java # src/test/java/com/launchdarkly/client/LDClientEvaluationTest.java # src/test/java/com/launchdarkly/client/LDClientOfflineTest.java
fix default value logic
avoid some inappropriate uses of Guava's ImmutableMap
…easons # Conflicts: # src/main/java/com/launchdarkly/client/FeatureFlagsState.java
don't keep evaluating prerequisites if one fails
add tests for JSON serialization of evaluation reasons
…ith-reasons evaluation reasons can be included in allFlagsState()
update doc comment for track() with metric
avoid concurrency problem with date parser for event responses
add tests and doc comments about float->int rounding
…experimentation-events"" This reverts commit 1c49f9b.
better exceptions for null params
…ent-and-proxy apply proxy settings to stream, and manage HTTP clients better
bwoskow-ld
approved these changes
Oct 17, 2019
LaunchDarklyCI
pushed a commit
that referenced
this pull request
Jan 17, 2020
don't include exception in error reason JSON rep
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.
[4.8.1] - 2019-10-17
Fixed:
Class.forName()for a class name that was accidentally transformed by the Shadow plugin for Gradle. (#171)LDConfig.Builder.proxy()andLDConfig.Builder.proxyAuthenticator(). (#172)OkHttpClientinstance as part of the staticLDConfiginstance used by theLDClient(String)constructor. This has been removed.sdkKeyorconfigto theLDClientconstructors would always throw aNullPointerException, but it did not have a descriptive message. These exceptions now explain which parameter was null.