Skip to content
This repository was archived by the owner on May 30, 2024. It is now read-only.

Conversation

@eli-darkly
Copy link
Contributor

[5.2.0] - 2018-08-01

Changed:

  • The promise from waitForInitialization(), if successful, now resolves with a value: the client. Previously, it resolved with no value. (Thanks, rmanalan!)

Fixed:

  • Receiving an HTTP 400 error from LaunchDarkly should not make the client give up on sending any more requests to LaunchDarkly (unlike a 401 or 403).

atrakh and others added 19 commits July 11, 2018 10:55
…hods-to-typescript-definitions

[ch20232] Add flag util methods to typescript definitions
The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/npm:cryptiles:20180710
[Snyk] Fix for 1 vulnerable dependencies
remove npm dependency on "crypto", use built-in version instead
treat HTTP 400 as a recoverable error
update doc comment for new waitForInitialization behavior
fix waitForInitialization to always resolve with a value
@eli-darkly eli-darkly requested a review from apucacao August 1, 2018 22:52
@eli-darkly eli-darkly merged commit 7d505e8 into master Aug 1, 2018
@eli-darkly eli-darkly deleted the 5.2.0 branch August 1, 2018 22:56
eli-darkly added a commit that referenced this pull request Nov 14, 2018
add tests for CachingStoreWrapper + misc bug fixes
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants