Don't overwrite custom user defined event id - #884
Closed
Seltsamsel wants to merge 1 commit into
Closed
Conversation
Contributor
|
Thanks for the PR @mcepok We're well on the way to v3 now which sees a significant reshuffle of the codebase. I'm happy to include this change in v3. If you want to build your own version of |
Author
|
We actually want this behavior for the snowplow-nodejs-tracker which, as far as I understood, is based since version 0.4.0 on the core-tracker of this repository. If the next release of the core-tracker is coupled with the javascript-tracker release, that's also fine. Thanks a lot! |
Paul Boocock (paulboocock)
self-requested a review
February 11, 2021 11:46
Paul Boocock (paulboocock)
approved these changes
Feb 11, 2021
Merged
20 tasks
Contributor
|
I've cherry-picked this into the release/3.0.0 branch and opened corresponding issue #911 |
This file contains hidden or 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
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.
In some cases, we already set an event id provided via
payloadPairsand it's important for us to keep that event id. However, currently in the core tracker the event id is overwritten no matter what. One very simple solution to this issue is to switch the order of adding the event id and thepayloadPairs. In the normal way of using the tracker without providing an own event id, nothing changes.