Update UI Event Transaction the same event same ui element scenario#856
Update UI Event Transaction the same event same ui element scenario#856krystofwoldrich merged 3 commits intomasterfrom
Conversation
krystofwoldrich
requested review from
0Calories,
k-fish,
philipphofmann and
romtsn
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
krystofwoldrich
changed the title
0Calories
left a comment
0Calories
left a comment
There was a problem hiding this comment.
These scenarios look good to me, thanks @krystofwoldrich !
philipphofmann
left a comment
philipphofmann
left a comment
There was a problem hiding this comment.
Thanks for updating the develop docs accordingly, @krystofwoldrich 👏 . A few issues to address.
Co-authored-by: Philipp Hofmann <[email protected]>
|
@philipphofmann Thanks for the meta issue and for the suggestions. |
| Given an ongoing UI event transaction | ||
| When the user triggers the same UI element with a new event | ||
| Or the user triggers a different UI element | ||
| Then the SDK discards the transaction |
There was a problem hiding this comment.
@krystofwoldrich what does "discard" mean exactly here? Does it mean finish the previous transaction as cancelled/aborted or does it mean drop the transaction or does it mean finish it normally but remove from scope? I guess this needs clarification
There was a problem hiding this comment.
I agree this should be more explicit, so there can't be multiple ways of interpreting it.
The way I understood it was not to sample/drop the transaction.
4 participants
Based on the discussion here:
I think we should update the develop docs and open issues for SDKs that already implemented the current scenarios to update it.