-
Notifications
You must be signed in to change notification settings - Fork 35
Return eventId from Tracker.track() (close #304) #310
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
Changes from all commits
8e20735
50c274f
1ff0165
fd9c5d0
1b06ae6
eec1ce0
3d0b317
cfb5d5e
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -209,7 +209,7 @@ public TrackerPayload getPayload() { | |
| payload.add(Parameter.TR_STATE, this.state); | ||
| payload.add(Parameter.TR_COUNTRY, this.country); | ||
| payload.add(Parameter.TR_CURRENCY, this.currency); | ||
| return putDefaultParams(payload); | ||
| return putTrueTimestamp(payload); | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This code is quite ugly because the AbstractEvent tries to cover both types of events: SelfDescribing and atomic (primitive) events. Otherwise we could use A correct distinction between SelfDescribing and Primitive would help to write the code in this way. and the abstract class would have... Anyway, for now we can't do anything like this. It's ok until we don't change the way the events work in the tracker. |
||
| } | ||
|
|
||
| /** | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So pitiful that those legacy eCommerce transaction events force us to do this :(
I'm wondering... what if we return just the eventID of the transaction event without the eventID of all the ecommerce items events?
Essentially those item events are like entities tracked as events due to legacy.
BTW, just an idea, let's keep this as you implemented now.