prepare 5.2.0 release #107
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
log exceptions at error level and stacktraces at debug level
add new version of all_flags that captures more metadata
add ability to filter for only client-side flags
implement evaluation with explanations
fix event generation for a prerequisite that is off
zsiddique
approved these changes
Aug 30, 2018
|
The FOSSA warning started prior to the last release, and isn't related to any code change as far as I can tell, so their own process must have changed. It's a development-only dependency, so not a priority at the moment - it would be good to make it go away but I'm not sure how much we can really do about it. |
eli-darkly
added a commit
that referenced
this pull request
Mar 21, 2019
include user in prereq flag events
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.2.0] - 2018-08-29
Added:
LDClientmethodvariation_detailallows you to evaluate a feature flag (using the same parameters as you would forvariation) and receive more information about how the value was calculated. This information is returned in anEvaluationDetailobject, which contains both the result 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.Fixed: