Fix "ping" event #3521
Merged
Fix "ping" event #3521
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This Pull Request targets Consider targeting |
This is fixing something in develop |
bpmn-io-tasks
bot
added
needs review
smbea
requested review from
a team,
philippfromme and
marstamm
and removed request for
a team
nikku
approved these changes
Mar 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #3486
Context:
The "ping" event was not being sent initially because it was being configured before Mixpanel was enabled. I added
tracking.enabled/tracking.disabledemitted events to manage this.This didn't happen before because previous events are only triggered via user actions. With "ping", we want to send it specifically after tracking has been enabled.