-
Notifications
You must be signed in to change notification settings - Fork 7
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
Wrong page tracked when user comes back after checkout #540
Conversation
@@ -11,8 +11,6 @@ import { checkoutDidEnter$ } from '../streams/checkout'; | |||
*/ | |||
export default function checkout(subscribe) { | |||
subscribe(checkoutDidEnter$, ({ getState }) => { | |||
setPWAVisibleState(false); |
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.
This change affects the pageview
events, which are dispatched for users who where not logged in when they entered the checkout. For them the system will now track an additional pageview for the cart
right after initiatedCheckout
.
That happens because APP_EVENT_VIEW_DID_DISAPPEAR
is triggered after the history.pop()
which is called to remove the login page from the PWA history stack.
const routeDidEnterForVisiblePwa$ = routeDidEnter$ | ||
.withLatestFrom(appWillStart$.merge(pwaVisibility$)) | ||
.filter(([, { action: { type } }]) => type === APP_WILL_START || type === PWA_DID_APPEAR) | ||
.map(([routeDidEnter]) => routeDidEnter); |
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.
5469cc1
to
bf80fcb
Compare
Pull Request Test Coverage Report for Build 2027
💛 - Coveralls |
Description
Wrong page tracked when user comes back after checkout
Type of change
Please add an "x" into the option that is relevant: