-
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
Customer Home: explicitly exclude VIP sites from loading Customer Home #39090
Conversation
I expect this will also need handling in the site selector for the |
Good catch @kwight I can add that |
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: App Entrypoints (~17 bytes added 📈 [gzipped])
Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used. Sections (~774 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. |
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.
@@ -3887,5 +3894,19 @@ describe( 'selectors', () => { | |||
canCurrentUserUseCustomerHome( createState( { created_at: '2020-01-01', jetpack: true } ) ) | |||
).toBe( false ); | |||
} ); | |||
|
|||
test( 'should return false for VIP site', () => { |
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.
Thanks for adding these tests ❤️
This PR makes sure that Customer Home will not load for VIP sites for now.
Testing Instructions
/client/state/sites/selectors/can-current-user-use-customer-home.js
commented out