-
Notifications
You must be signed in to change notification settings - Fork 1
Set entityId
on flag evaluation
#234
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
Conversation
4b7e842
to
d1b3915
Compare
Test failures are caused by |
extraLogging: split.extraLogging ?? {}, | ||
doLog: allocation.doLog, | ||
flagEvaluationDetails, | ||
entityId: flag.entityId ?? null, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤦🏽
Similar fix to js-client#182 is required here. |
PR/235 sent to fix the test suite. |
f631c24
to
2d513d6
Compare
allocationKey: precomputedFlag.allocationKey ?? '', | ||
extraLogging: precomputedFlag.extraLogging ?? {}, | ||
doLog: precomputedFlag.doLog, | ||
entityId: null, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this something that needs to be returned from the assignments endpoint so that the precomputed client has it available as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In order to support automated event logging for the precomputed mode, yes we'll have to pass that down as well.
Motivation and Context
Entity IDs are not being passed through to the assignment logger.
Description
Sets the entity ID on the flag evaluation object.
How has this been tested?