Skip to content
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

Stepper: Record calypso_signup_start unconditionally => multiple logs #94743

Merged
merged 1 commit into from
Sep 23, 2024

Conversation

chriskmnds
Copy link
Contributor

@chriskmnds chriskmnds commented Sep 20, 2024

Related to #94175
Fixes #94717

Proposed Changes

Records calypso_signup_start event unconditionally. This means it can get logged not only on the first step but on any of the dependencies changing.

extraProps coming from useSignupStartEventProps are guaranteed now to be logged as they change through flow progression.

Why are these changes being made?

Addressed #94175 (comment)

Testing Instructions

  • Go to /setup/onboarding
  • Ensure you see calypso_signup_start being recorded when logging in and on refreshing the page

Pre-merge Checklist

  • Has the general commit checklist been followed? (PCYsg-hS-p2)
  • Have you written new tests for your changes?
  • Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
  • Have you checked for TypeScript, React or other console errors?
  • Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
  • Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
  • For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

@chriskmnds chriskmnds self-assigned this Sep 20, 2024
@chriskmnds chriskmnds requested a review from a team as a code owner September 20, 2024 04:35
@matticbot matticbot added [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. labels Sep 20, 2024
@matticbot
Copy link
Contributor

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

App Entrypoints (~93 bytes removed 📉 [gzipped])

name           parsed_size           gzip_size
entry-stepper       -198 B  (-0.0%)      -93 B  (-0.0%)

Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

@chriskmnds chriskmnds mentioned this pull request Sep 20, 2024
7 tasks
@chriskmnds chriskmnds requested a review from a team September 20, 2024 04:43
Copy link
Contributor

@escapemanuele escapemanuele left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested it and the event is triggered with every refresh 👍

@renancarvalho
Copy link
Contributor

renancarvalho commented Sep 20, 2024

This is working fine!

I got confused, is this the same as this? If so, I think I can close my PR then?

@escapemanuele
Copy link
Contributor

@chriskmnds just noting that this PR will also fix this comment, since elapsed_time_since_start on calypso_signup_complete is now null if calypso_signup_start is not triggered ✌️

@renancarvalho yes, as pointed out in your PR 👍

@chriskmnds
Copy link
Contributor Author

This is working fine!

I got confused, is this the same as this? If so, I think I can close my PR then?

@renancarvalho It's something like part of a long story we've been drilling around for a few weeks #94175 (and related PR #94248 )

It is an alternative to your PR (and any other approach that ignores dependencies like "extra props" from retriggering the event), so if we ship this then we can close yours. Shipping this means also closing @gabrielcaires' PR: #94248

I want to get everyone involved/aware around #94175 so nobody's surprised if multiple events triggering show up in discussions. I intend to follow up similarly with other events :-)

@chriskmnds just noting that this PR will also fix #94706 (review), since elapsed_time_since_start on calypso_signup_complete is now null if calypso_signup_start is not triggered ✌️

Thanks @escapemanuele! Cool :D

@chriskmnds
Copy link
Contributor Author

Thank you all for reviewing! and for buying into this idea of "unconditional tracking" 🙈
Merging, and grabbing #94767 to address next

@chriskmnds chriskmnds merged commit fedfbd6 into trunk Sep 23, 2024
17 of 18 checks passed
@chriskmnds chriskmnds deleted the update/stepper-tracking-sigup-start-unconditional branch September 23, 2024 11:08
@github-actions github-actions bot removed the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Stepper: calypso_signup_start not being triggered on refresh
4 participants