-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Publish a Blog: Add feature flag and pass it to site creation endpoint #99484
base: trunk
Are you sure you want to change the base?
Conversation
Jetpack Cloud live (direct link)
Automattic for Agencies live (direct link)
|
client/landing/stepper/declarative-flow/internals/steps-repository/create-site/index.tsx
Show resolved
Hide resolved
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: Sections (~1119 bytes added 📈 [gzipped])
Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to. 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. |
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 |
client/landing/stepper/declarative-flow/internals/steps-repository/create-site/index.tsx
Show resolved
Hide resolved
@@ -234,7 +237,8 @@ const CreateSite: Step = function CreateSite( { navigation, flow, data } ) { | |||
domainItem, | |||
sourceSlug, | |||
siteIntent, | |||
shouldSaveSiteGoals ? siteGoals : undefined | |||
shouldSaveSiteGoals ? siteGoals : undefined, | |||
config.isEnabled( 'onboarding/write-goal' ) |
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.
Should we also do a treatment_cumulative
check here?
489a460
to
c4cc2c7
Compare
@@ -234,7 +239,9 @@ const CreateSite: Step = function CreateSite( { navigation, flow, data } ) { | |||
domainItem, | |||
sourceSlug, | |||
siteIntent, | |||
shouldSaveSiteGoals ? siteGoals : undefined | |||
shouldSaveSiteGoals ? siteGoals : undefined, | |||
isGoalsFirstCumulativeExperience && |
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.
I'm wondering if we should include the treatment_cumulative
checks right now. It's under a feature flag, so it will only work for explicitly-enabled people. I wonder if we should only check for the experiment when it's time to remove the flag.
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.
🤷 Either options's fine. Putting it in now means at least we know we've remembered to add that logic.
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.
I say we leave the isGoalsFirstCumulativeExperience check in there.
c4cc2c7
to
67a362f
Compare
67a362f
to
6c8c580
Compare
Closes #99453.
Testing Instructions
Checkout 172681-ghe-Automattic/wpcom in your sandbox and proxy yourself.
onboarding/enable-write-goal-features
feature flag and go to/setup/onboarding
write
intent on the site)/settings/newsletter/%s
and verify that the "Add the Subscribe Block at the end of each post." toggle is ON.Create a site in a different flow or by picking different goals and verify that the the toggle is OFF in the Newsletter settings.