-
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
Goals first: Enable back button in the login step for the DIFM and Import flows #97722
Goals first: Enable back button in the login step for the DIFM and Import flows #97722
Conversation
Jetpack Cloud live (direct link)
Automattic for Agencies live (direct link)
|
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: Sections (~259 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. Async-loaded Components (~75 bytes added 📈 [gzipped])
React 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. |
client/signup/steps/user/index.jsx
Outdated
@@ -753,9 +753,13 @@ export class UserStep extends Component { | |||
return null; | |||
} | |||
|
|||
const backUrl = this.props.backUrl?.startsWith( '/' ) ? this.props.backUrl : undefined; |
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.
non-blocking: maybe move this piece into the connect
wrapper
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.
04c6218
to
718900a
Compare
Thanks @vykes-mac this should be ready to go now |
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.
LGTM
…port flows (#97722) * Accept back_url query parameter in signup/user * Accept back_url query parameter in setup/hosted-site-migration * Add back_url to DIFM and hosted-site-migration flows * Move back_url conciliation within redux connect function * Update implementation so it uses back_to instead of back_url * Push back button to the right so it doesn't conflict with the WP Logo * Update unit tests
Closes #97706.
Proposed Changes
Title. I'm not sure if the chosen approach here is the best - please let me know if there's a better way of achieving it for both flows.
Why are these changes being made?
Continuity, UX.
Testing Instructions
Enter
/setup/onboarding
and click the DIFM link. You should be redirected to the login screen with the back button enabled and that button should send you back to the goals screen.Do the same for the import link in the goals step.