Skip to content

fix: setup context for emitting event to segment if desired #36692

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

Merged
merged 1 commit into from
May 9, 2025

Conversation

justinhynes
Copy link
Contributor

Description

If we wish this event to be sent to Segment through the event-tracking lib, we must ensure that the context includes at least the user_id field in the context dict.

If we wish this event to be sent to Segment through the event-tracking lib, we must ensure that the context includes at least the `user_id` field in the context dict.
@justinhynes justinhynes marked this pull request as ready for review May 9, 2025 14:21
@justinhynes justinhynes merged commit f509bce into master May 9, 2025
49 checks passed
@justinhynes justinhynes deleted the jhynes/APER-3967_error_handling branch May 9, 2025 14:54
@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

@edx-pipeline-bot
Copy link
Contributor

2U Release Notice: This PR has been deployed to the edX production environment.

UsamaSadiq pushed a commit that referenced this pull request May 14, 2025
If we wish this event to be sent to Segment through the event-tracking lib, we must ensure that the context includes at least the `user_id` field in the context dict.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants