-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 5.3.1 #232
Merged
Merged
Release 5.3.1 #232
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
…hanged TimeInterval to Date, changed two inout's to var's
Rebuilt Connection Status, added unit tests, fixed warnings
…and wasOnline is false
Add Identify method
…tream close listener
Also removed unused test code. Improve documentation on LDClient.flush()
…brary in SwiftPM build. (#121)
…es in all cases (#123)
Allow dynamic configuration of http headers through LDConfig.headerDelegate
…130) * Removed FlagStore from LDUser * All unit tests build and LDClientSpec doesn't crash * Fixed 1 unit test, removed unnecessary testing parameter in internalIdentify * Fixed 29 unit tests * Fixed 26 unit tests * Fix all but 4 unit tests * Removed comment * Addressed PR feedback * Removed unnecessary for each in LDUserSpec * Removed unnecessary contexts in LDUserSpec, removed user value in FlagChangeNotifierSpec * Fixed LDUserSpec context, added stub flags to DarklyServiceSpec * Make LDClientSpec init less hacky * Clear FlagStore if new user does not have cached flags, make flagStore a let * Added FlagStore back to LDUser for init from flag dictionary, check for user.flagStore on LDClient init and identify * Added deprecation comment to dictionary init for LDUser, prioritize LDUser FlagStore over cache in identify * Changed identify ordering back to cache over flagstore, made FlagStore a let
gwhelanLD
approved these changes
Dec 16, 2020
keelerm84
added a commit
that referenced
this pull request
Jun 5, 2023
TLS 1.1 has been deprecated for a long time and has been dropped by most major providers. The LaunchDarkly APIs haven't accepted anything lower than TLS 1.2 for a long time. We are therefore forcing TLS 1.2 as the minimum going forward in this library.
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.
[5.3.1] - 2020-12-15
Fixed
FlagStore
fromLDUser
to fix a bug where multiple environments could overwrite each other's flag values.