This repository was archived by the owner on May 30, 2024. It is now read-only.
Conversation
fix allFlagsState behavior when options are omitted
validate TypeScript definitions in CI build
# Conflicts: # test/LDClient-test.js
implement evaluation with explanation
fix error handling for malformed flags
prevent unhandled rejection from background flush
remove unused "hoek" dependency
This reverts commit 7d8d074.
This reverts commit 587b777.
This reverts commit 6af73a8.
…ncy)"" This reverts commit 81c3aad.
don't signal init failure & don't fire an error unless it's unrecoverable
remove typedoc dependency
use semver 6.x
* update eslint to 6.x * use CircleCI 2.1 syntax * typo * rm unused * minor cleanup * syntax fix * add job names
# Conflicts: # .circleci/config.yml
fix some vulnerable npm dependencies and add a better way to catch them
better handling of invalid data types
atrakh
approved these changes
Oct 23, 2019
bwoskow-ld
approved these changes
Oct 23, 2019
LaunchDarklyCI
pushed a commit
that referenced
this pull request
Feb 12, 2020
…ream diagnostic events, part 3: capture stream connection stats
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
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.9.2] - 2019-10-23
Changed:
updateevents were receiving an entire flag configuration object as an argument. This was not useful for applications (since the SDK does not provide any way to use such an object directly), and was unsafe since the object was shared with internal code and was mutable. The argument forupdateevents is now an object with only one property,key(the flag key).npm auditdetects any vulnerabilities in the runtime dependencies (not includingdevDependencies).Fixed:
setTimeoutto defer callbacks. These have been replaced withsetImmediatefor callbacks into application code, or with direct undeferred callbacks in internal code paths where it is safe to do so. (Thanks, mdgbayly!)waitForInitializationpromise and should not emit anerrorevent. (#155)startsWithshould only be able to match if both values are strings; numeric operators such aslessThanshould only be able to match if both values are numbers; strings should only be usable as date/time values if they match RFC3339 format; and invalid regexes should simply cause a non-match, rather than an error.updateevent would only be triggered for a flag if that flag's configuration were changed directly; it did not take into account indirect changes that could affect a flag's value, such as a change to one of its prerequisite flags or to a user segment that it references. This has been fixed so that any change potentially affecting a flag's value will produce anupdateevent for that flag.LDFeatureStore.upsert()was wrong. (Thanks, JakeGinnivan!)hoek. (#158)semver. (Thanks, mmcgahan!)npm audit.