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

Signup form: Accept a custom "handleLogin" function prop #41800

Merged
merged 5 commits into from
Jun 9, 2020

Conversation

DanReyLop
Copy link
Contributor

Changes proposed in this Pull Request

In d9c6ba4, make the WooCommerce version of the SignupForm block respect the footerLink prop. That prop already existed, but was only being used in the other branches of the SignupForm block, here and here.

In 92d2cc0, added an optional handleLogin prop to the SignupForm block. This function, if it exists, will be called when the "login" link is clicked, instead of making a full-page redirect to the login form.
Screenshot 2020-05-05 at 10 26 06

How to test

This is just a refactor, there shouldn't be any regression. At this moment, SignupForm is never called with a handleLogin prop, nor is called with a custom footerLink on the WooCommerce flow.

Note: This is a required refactor for the new "Woo DNA" flow, implemented in #41798

@DanReyLop DanReyLop added [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. [Feature] Signup & Account Creation All screens and flows for making a new WordPress.com account. labels May 5, 2020
@DanReyLop DanReyLop requested a review from a team May 5, 2020 13:03
@matticbot
Copy link
Contributor

@matticbot
Copy link
Contributor

matticbot commented May 5, 2020

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

App Entrypoints (~11 bytes added 📈 [gzipped])

name         parsed_size           gzip_size
entry-login        +41 B  (+0.0%)      +11 B  (+0.0%)

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

Sections (~100 bytes added 📈 [gzipped])

name             parsed_size           gzip_size
jetpack-connect       +193 B  (+0.0%)      +50 B  (+0.0%)
accept-invite         +193 B  (+0.1%)      +50 B  (+0.1%)

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 (~53 bytes added 📈 [gzipped])

name                          parsed_size           gzip_size
async-load-signup-steps-user       +193 B  (+0.2%)      +50 B  (+0.2%)
async-load-design-blocks            +41 B  (+0.0%)       +3 B  (+0.0%)

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.
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.

Copy link
Contributor

@vbelolapotkov vbelolapotkov left a comment

Choose a reason for hiding this comment

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

@DanReyLop the changes look good and straightforward. Do you have any idea why ci/wp-desktop check fails?

Copy link
Contributor

@vbelolapotkov vbelolapotkov left a comment

Choose a reason for hiding this comment

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

I've taken a look at the checks in this commit d9c6ba4 and see ci/wp-desktop was passing. I doubt the following commit with style fixing is causing it to fail, so go to go IMO.

@vbelolapotkov vbelolapotkov added [Status] Ready to Merge and removed [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. labels May 26, 2020
@DanReyLop
Copy link
Contributor Author

I've taken a look at the checks in this commit d9c6ba4 and see ci/wp-desktop was passing. I doubt the following commit with style fixing is causing it to fail, so go to go IMO.

Thanks for investigating! You're right, the wp-desktop failure is probably unrelated.

I'll wait to merge this until I have a bunch of them to merge, there's going to be a lot of Git gardening involved and the more times I need to do it, the more possibilities of messing it up.

@DanReyLop DanReyLop force-pushed the woodna/login-block-enhancements branch from 8389cd2 to 00921f4 Compare June 8, 2020 12:04
@DanReyLop DanReyLop force-pushed the woodna/signup-block-enhancements branch from 3db003a to 085164c Compare June 8, 2020 12:05
Base automatically changed from woodna/login-block-enhancements to master June 9, 2020 13:19
@DanReyLop DanReyLop merged commit e7cbfc9 into master Jun 9, 2020
@DanReyLop DanReyLop deleted the woodna/signup-block-enhancements branch June 9, 2020 13:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Signup & Account Creation All screens and flows for making a new WordPress.com account.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants