-
Notifications
You must be signed in to change notification settings - Fork 4
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
feat: AssignmentTrackingProvider used to track local evaluation assignment events #14
Conversation
On PR summary comment you mention that we could do Assignment::toJSONPayload or Assignment::toJSONString but this methods are not static so I guess that we should do something like:
Is this correct? |
Yes, that is correct. |
# [0.5.0](0.4.0...0.5.0) (2024-02-15) ### Features * AssignmentTrackingProvider used to track local evaluation assignment events ([#14](#14)) ([62a6696](62a6696))
🎉 This PR is included in version 0.5.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Summary
AssignmentTrackingProvider interface
AssignmentConfig
to send assignment events from local evaluations to Amplitudetrack
method takes in an Assignment object, which represents an assignment eventAssignment::toJSONPayload
can be used to convert an Assignment to a JSON string representation of the payload required to send an event to AmplitudeAssignment::toJSONString
can be used to convert an Assignment to a JSON string representation of an assignment event - this is equivalent to an object in theevents
array in the payloadDefaultAssignmentTrackingProvider
Refactors
minIdLength
(minimum permitted length foruser_id
anddevice_id
fields for assignment event) added toAssignmentConfig
logger
added toAmplitudeConfig
instead of being passed viaLocaEvaluationClient
toEvent
moved fromAssignmentService
toAssignment