-
Notifications
You must be signed in to change notification settings - Fork 2k
Remove unused createWithBigSky from onboard datastore
#102442
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
Conversation
Jetpack Cloud live (direct link)
Automattic for Agencies live (direct link)
|
|
This PR modifies the release build for the following Calypso Apps: For info about this notification, see here: PCYsg-OT6-p2
To test WordPress.com changes, run |
|
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: App Entrypoints (~54 bytes removed 📉 [gzipped]) DetailsCommon code that is always downloaded and parsed every time the app is loaded, no matter which route is used. Sections (~63 bytes added 📈 [gzipped]) DetailsSections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to. Async-loaded Components (~155 bytes added 📈 [gzipped]) DetailsReact components that are loaded lazily, when a certain part of UI is displayed for the first time. 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. Generated by performance advisor bot at iscalypsofastyet.com. |
a1bf562 to
7664687
Compare
5a105ef to
8762019
Compare
7664687 to
4afae7f
Compare
8762019 to
37dd93b
Compare
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.
Copilot reviewed 8 out of 8 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (2)
client/my-sites/plans-features-main/components/plan-upsell-modal/paid-plan-is-required-dialog.tsx:31
- The removal of createWithBigSky conditions alters the modal messaging logic; please confirm that the new default messaging aligns with the intended user experience.
if ( createWithBigSky && paidDomainName ) { return translate( 'Domains and our AI Website Builder are only available with a paid plan' ); }
client/my-sites/plans-features-main/components/plan-upsell-modal/hooks/use-modal-resolution-callback.tsx:47
- By removing this branch, modal resolution may handle certain onboarding flows differently; ensure this change is fully consistent with the updated business logic.
if ( createWithBigSky && ONBOARDING_FLOW === flowName ) { return PAID_PLAN_IS_REQUIRED_DIALOG; }
p-jackson
left a comment
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.
Yes this is exactly right thanks @ciampo
The createWithBigSky state was necessary for the goals-first onboarding flow because we needed to know how it was the user had arrived at the plans step. The goals-step is no more, so the state is no longer used.
Related to #101759
Related to DOTOBRD-36
Extracted from #101921
Proposed Changes
Remove unused
createWithBigSkyfrom onboard datastoreWhy are these changes being made?
With the removal of goals-first onboarding (see #101759 (comment)) , I realized that
setCreateWithBigSkyaction is only called once, withfalse— meaning that we can clean up all usages ofgetCreateWithBigSky, assuming that it will always returnfalse(and we can clean up the data-store too).Testing Instructions
createWithBigSkydata from the onboard data store is never set to anything different thanfalsetrunkPre-merge Checklist