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

Jetpack section: Add Jetpack tab to Settings section #43138

Merged
merged 3 commits into from
Jun 10, 2020

Conversation

cleacos
Copy link
Contributor

@cleacos cleacos commented Jun 10, 2020

Changes proposed in this Pull Request

Add a new Jetpack subsection-tab to the Settings sections in Calypso and move the Credential block to it.

(note: in this PR the Credential block is the Credential component from Calypso and not from cloud. On an upcoming PR we'll set the Credential component from cloud.

Testing instructions

  • Apply this change
  1. yarn start-jetpack-section if not, use the flags query ?flags=jetpack/features-section
  2. Select a Jetpack site and go to the Settings section, you'll see the new Jetpack tab
  3. Click on the Jetpack tab and you should see the Credential block (with a connected or disconnected status)
  4. Click on the Security tab, you shouldn't see the Credential block and you'll see a banner with a CTA that will take you to the Jetpack tab, click on that CTA and check if it takes you to the Jetpack tab.
  • Now deactivate the Jetpack features-section with this query: ?flags=-jetpack/features-section
  • Check again the point 2: now you shouldn't see the Jetpack tab
  • Check again the point 4: now you should see the Credential block as always.

@cleacos cleacos added [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. Jetpack Cloud Anything related to the Jetpack Cloud (cloud.jetpack.com) labels Jun 10, 2020
@cleacos cleacos requested review from ChaosExAnima, rcanepa and a team June 10, 2020 10:42
@cleacos cleacos self-assigned this Jun 10, 2020
@matticbot
Copy link
Contributor

@matticbot
Copy link
Contributor

matticbot commented Jun 10, 2020

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

Webpack Runtime (~406 bytes added 📈 [gzipped])

name      parsed_size           gzip_size
manifest      +1313 B  (+0.7%)     +406 B  (+1.1%)

Webpack runtime for loading modules. It is included in the HTML page as an inline script. Is downloaded and parsed every time the app is loaded.

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

name        parsed_size           gzip_size
entry-main      +1208 B  (+0.1%)      +59 B  (+0.0%)

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

Sections (~60409 bytes added 📈 [gzipped])

name                  parsed_size           gzip_size
settings-jetpack        +209823 B    (new)   +58384 B    (new)
settings-security         +1206 B  (+0.5%)    +1689 B  (+2.4%)
settings-writing           +201 B  (+0.0%)      +36 B  (+0.0%)
settings-performance       +201 B  (+0.1%)      +41 B  (+0.1%)
settings-discussion        +201 B  (+0.1%)      +35 B  (+0.1%)
settings                   +201 B  (+0.0%)      +33 B  (+0.0%)
activity                   +104 B  (+0.0%)     +673 B  (+0.6%)
stats                       +46 B  (+0.0%)     -489 B  (-0.2%)
signup                      +40 B  (+0.0%)       +7 B  (+0.0%)

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

@rcanepa rcanepa left a comment

Choose a reason for hiding this comment

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

LGTM! I tested both cases and they worked as expected.

@rcanepa
Copy link
Contributor

rcanepa commented Jun 10, 2020

@cleacos, I think there is still one more thing to do. @keoshi commented in #43125 that we should include the highlight mentioned here: #40018

@cleacos
Copy link
Contributor Author

cleacos commented Jun 10, 2020

@rcanepa okay, thanks. Let's do it in another PR

@cleacos cleacos merged commit 09cbaab into master Jun 10, 2020
@cleacos cleacos deleted the move/jetpack-cloud-setting-section-to-wp-jetpack-tab branch June 10, 2020 15:14
@matticbot matticbot removed the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Jun 10, 2020
@a8ci18n
Copy link

a8ci18n commented Jun 10, 2020

This Pull Request is now available for translation here: https://translate.wordpress.com/deliverables/3797383

Hi @cleacos, could you please edit the description of this PR and add a screenshot for our translators? Ideally it'd include this string: No Jetpack configuration is required.

Thank you in advance!

@a8ci18n
Copy link

a8ci18n commented Jun 17, 2020

Translation for this Pull Request has now been finished.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Jetpack Cloud Anything related to the Jetpack Cloud (cloud.jetpack.com)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants