This repository has been archived by the owner on May 30, 2024. It is now read-only.
prepare 5.2.3 release #225
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
…ates-intf-1 (#4) rename DataStoreUpdates to DataSourceUpdates
…ates-intf-2 (#5) add a new DataStoreUpdates that's for the data store to use
# Conflicts: # src/test/java/com/launchdarkly/sdk/server/LDClientListenersTest.java # src/test/java/com/launchdarkly/sdk/server/StreamProcessorTest.java
# Conflicts: # src/main/java/com/launchdarkly/client/Components.java # src/main/java/com/launchdarkly/client/EventsConfiguration.java # src/main/java/com/launchdarkly/sdk/server/DefaultEventProcessor.java # src/main/java/com/launchdarkly/sdk/server/EventFactory.java # src/main/java/com/launchdarkly/sdk/server/integrations/EventProcessorBuilder.java # src/test/java/com/launchdarkly/client/TestUtil.java # src/test/java/com/launchdarkly/sdk/server/DefaultEventProcessorTest.java
# Conflicts: # src/test/java/com/launchdarkly/sdk/server/LDClientEndToEndTest.java
…add new ErrorKind for this; improve comments and tests
(#6) implement data source status monitoring
# Conflicts: # src/main/java/com/launchdarkly/sdk/server/DefaultEventProcessor.java
decouple event HTTP logic from event processing
# Conflicts: # src/main/java/com/launchdarkly/sdk/server/DefaultEventSender.java # src/test/java/com/launchdarkly/sdk/server/DefaultEventSenderTest.java
…e-url make events URI construction reliable regardless of whether base URI ends in a slash
# Conflicts: # CHANGELOG.md # build.gradle # gradle.properties # src/main/java/com/launchdarkly/client/value/LDValue.java # src/main/java/com/launchdarkly/sdk/server/interfaces/LDClientInterface.java # src/test/java/com/launchdarkly/client/LDUserTest.java # src/test/java/com/launchdarkly/client/value/LDValueTest.java
…on return types (#268)
…stupdate [ch90672] socket factory make test less ambiguous
…275) * increment versions when loading file data, so FlagTracker will work * update doc comment about flag change events with file data
bwoskow-ld
approved these changes
Feb 19, 2021
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.
[5.2.3] - 2021-02-19
Fixed:
FlagTrackerdid not work when the data source wasFileData. This has been fixed so that wheneverFileDatareloads the data file(s) due to a file being modified, it signals that the flags were updated. The SDK will behave as if every flag was updated in this case, regardless of which part of the file data was actually changed, but it was already the case that a flag change event did not necessarily mean there was any significant change to the flag. You can useaddFlagValueChangeListener(as opposed toaddFlagChangeListener) to be notified only of changes that affect a specific flag's value for a specific user. (#224)