Skip to content
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

Initial support for tracking submissions with Segment #1872

Merged
merged 11 commits into from
Aug 27, 2020
Merged

Conversation

DavisRayM
Copy link
Contributor

Based on #1871

Changes / Features implemented

  • analytics module to track events

@DavisRayM DavisRayM changed the title Initial support for tracking submissions with Segment [WIP] Initial support for tracking submissions with Segment Aug 12, 2020
@DavisRayM DavisRayM self-assigned this Aug 12, 2020
@DavisRayM DavisRayM force-pushed the analytics branch 11 times, most recently from 2db3bcb to 5ebbffd Compare August 14, 2020 14:24
@DavisRayM DavisRayM force-pushed the analytics branch 5 times, most recently from efc44ea to 0b68e20 Compare August 26, 2020 17:13
@DavisRayM DavisRayM force-pushed the analytics branch 3 times, most recently from 1f3999c to 636a798 Compare August 27, 2020 06:50
@DavisRayM DavisRayM changed the title [WIP] Initial support for tracking submissions with Segment Initial support for tracking submissions with Segment Aug 27, 2020
Copy link
Contributor

@ivermac ivermac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @DavisRayM, I just wanted to mention that I really like the way you have made use of the class decorators which is very clean and easy to use. Good job on this 👍 !

@DavisRayM DavisRayM merged commit c276d51 into master Aug 27, 2020
@DavisRayM DavisRayM deleted the analytics branch August 27, 2020 08:02
This was referenced Aug 28, 2020
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