This repository was archived by the owner on May 30, 2024. It is now read-only.
prepare 4.9.0 release #174
Merged
Conversation
This file contains hidden or 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
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()
make LDUser serialize correctly as JSON and add more test coverage
preserve prerequisite flag value in event even if flag was off
more test coverage for requesting values of different types
send correct event schema version
new option for sending less bootstrap data based on event tracking status
change Gradle build to fix pom
# Conflicts: # scripts/release.sh
fix build so jar signatures will be published
# Conflicts: # packaging-test/Makefile
add LDValue type and deprecate use of JsonElement
add package comments
…tric restore previously existing track() overload
fix NewRelic reflection logic to avoid shading
better exceptions for null params
…ent-and-proxy apply proxy settings to stream, and manage HTTP clients better
# Conflicts: # src/test/java/com/launchdarkly/client/UtilTest.java
bwoskow-ld
approved these changes
Oct 18, 2019
gwhelanLD
approved these changes
Oct 18, 2019
eli-darkly
added a commit
that referenced
this pull request
Apr 30, 2020
(5.0 - #1) increase the minimum Java version all the way to 8!
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
7 participants
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.9.0] - 2019-10-17
This release adds the
LDValueclass (incom.launchdarkly.client.value), which is a new abstraction for all of the data types supported by the LaunchDarkly platform. Since those are the same as the JSON data types, the SDK previously used the Gson classesJsonElement,JsonObject, etc. to represent them. This caused two problems: the public APIs are dependent on Gson, and the Gson object and array types are mutable so it was possible to accidentally modify values that are being used elsewhere in the SDK.While the SDK still uses Gson internally, all references to Gson types in the API are now deprecated in favor of equivalent APIs that use
LDValue. Developers are encouraged to migrate toward these as soon as possible; the Gson classes will be removed from the API in a future major version. If you are only using primitive types (boolean, string, etc.) for your feature flags and user attributes, then no changes are required.There are no other changes in this release.
Added:
LDValue(see above).jsonValueVariationandjsonValueVariationDetailmethods inLDClient/LDClientInterfaceare equivalent toJsonVariationandJsonVariationDetail, but useLDValue.Deprecated:
LDClient/LDClientInterface:jsonVariation/jsonVariationDetail. UsejsonValueVariation/jsonValueVariationDetail.LDClient/LDClientInterface:track(String, LDUser, JsonElement)andtrack(String, LDUser, JsonElement, double). UsetrackData(String, LDUser, LDValue)andtrackMetric(String, LDUser, LDValue, double). The names are different to avoid compile-time ambiguity since bothJsonElementandLDValueare nullable types.LDUserBuilder:custom(String, JsonElement)andprivateCustom(String, JsonElement). Use theLDValueoverloads.LDValue:fromJsonElement,unsafeFromJsonElement,asJsonElement,asUnsafeJsonElement. These are provided for compatibility with code that still usesJsonElement, but will be removed in a future major version.