-
Notifications
You must be signed in to change notification settings - Fork 1
feat(events): New API EppoAssignmentLogger
#217
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
EppoAssignmentLogger
EppoAssignmentLogger
EppoAssignmentLogger
@petzel PTAL |
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.
The auto assignment source creation logic expects the fields of the event to match those of the IAssignmentEvent
, in snake case when applicable. I added suggestions for each field that needs to be updated.
Once those are applied, LGTM 🚢
experiment: 'experiment-abc', | ||
variant: 'control', | ||
entityId: 456, | ||
holdoutKey: 'holdout-xyz', |
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.
I see that holdoutKey
exists in other tests, but this field does not exist on IAssignmentEvent
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.
yeah I mentioned this in a code comment, it's confusing. this is the line:
https://github.com/Eppo-exp/js-sdk-common/blob/main/src/assignment-logger.ts#L48
IAssignmentEvent
can hold arbitrary key/value pairs from extraLogging
in FlagEvaluation
Co-authored-by: Eric Petzel <[email protected]>
Co-authored-by: Eric Petzel <[email protected]>
Co-authored-by: Eric Petzel <[email protected]>
labels: mergeable
Fixes: FF-3993
Motivation and Context
Implement
EppoAssignmentLogger
for seamless Eppo-managed assignment logging.Description
How has this been tested?
Wrote tests