-
Notifications
You must be signed in to change notification settings - Fork 68
prepare 2.6.0 release #112
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
Merged
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
This reverts commit c22d722.
override jsdom version to avoid test problems
change identify() result back to a key-value map like it used to be
[ch22054] Document the Promise polyfill and make all polyfill sections consistent
…hed NPM package (#94) TIL that `npm pack` will build the tarball that actually gets uploaded to the NPM servers. If you want to verify this works, ```sh npm run clean npm run prepublishOnly # simulate build that occurs before publishing npm pack # generate the tarball that will end up on NPM servers ``` Since we don't include anything from `src/`, I moved the TypeScript typings to the package root to avoid having to copy things around.
add check for $valid property
add reconnect logic to stream
add TypeScript syntax check
implement evaluation with explanations
reorganize and improve LDClient tests
fix allFlags
apucacao
approved these changes
Sep 7, 2018
eli-darkly
added a commit
that referenced
this pull request
Dec 7, 2018
6. move all goals logic into ldclient-js
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.
[2.6.0] - 2018-09-07
Added:
evaluationReasonscauses LaunchDarkly to report information about how each feature flag value was determined; you can access this information with the new client methodvariationDetail. The new method returns an object that contains both the flag value and a "reason" object which will tell you, for instance, if the user was individually targeted for the flag or was matched by one of the flag's rules, or if the flag returned the default value due to an error.Changed: