This repository has been archived by the owner on May 30, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 56
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
remove FOSSA upload step from CI
# Conflicts: # gradle.properties # src/main/java/com/launchdarkly/client/FeatureFlag.java # src/main/java/com/launchdarkly/client/LDClient.java
# Conflicts: # src/main/java/com/launchdarkly/client/LDClient.java
…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
add polling mode tests and end-to-end streaming test
revise custom TLS config implementation, add tests
add Redis builder options for password, TLS, database
# Conflicts: # src/main/java/com/launchdarkly/client/RedisFeatureStoreBuilder.java
# Conflicts: # src/test/java/com/launchdarkly/client/DefaultEventProcessorTest.java
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.
bwoskow-ld
approved these changes
Sep 27, 2019
LaunchDarklyCI
pushed a commit
that referenced
this pull request
Jan 16, 2020
preserve exception in evaluation reason
eli-darkly
added a commit
that referenced
this pull request
Jan 16, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.0] - 2019-09-27
Added:
LDClient.track(String, LDUser, JsonElement, double)
.Changed:
intVariation
to clarify the existing rounding behavior for floating-point values: they are rounded toward zero.