EvaluationContext each key should be unique#121
Merged
beeme1mr merged 6 commits intoAug 3, 2022
Conversation
Signed-off-by: Thomas Poignant <thomas.poignant@gofeatureflag.org>
beeme1mr
reviewed
Aug 3, 2022
Signed-off-by: Thomas Poignant <thomas.poignant@gofeatureflag.org>
96a2218 to
2d2ffa4
Compare
14e08e9 to
b19d87f
Compare
justinabrahms
approved these changes
Aug 3, 2022
beeme1mr
approved these changes
Aug 3, 2022
InTheCloudDan
approved these changes
Aug 3, 2022
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
Signed-off-by: Michael Beemer <michael.beemer@dynatrace.com>
This was referenced Aug 5, 2022
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Following the discussion here and this issue, I believe it is necessary to explicitly say that each key from the
EvaluationContextshould be unique.