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

Cleanup: deprecate the availability checks of the storage add-on #97391

Merged
merged 4 commits into from
Dec 16, 2024

Conversation

southp
Copy link
Contributor

@southp southp commented Dec 12, 2024

Proposed Changes

Now that the storage add-ons have become part of our standard offers, this PR removes the availability checks of the storage add-on, particularly within the use-add-on hook:

  • Remove all the storage add-on feature flag.
  • Remove enableStorageAddOn parameter since it's not in used.
  • Remove the function that checks if the storage add-on is enabled.

Why are these changes being made?

Since the storage add-ons are available by default now and there is no need for hiding them conditionally at the moment, cleaning the code up will ease the maintenance burden.

Testing Instructions

  • Confirm that the storage add-ons related UX works as expected in /add-ons.
  • Confirm that the storage add-on dropdown works as expected in /plans.

Pre-merge Checklist

  • Has the general commit checklist been followed? (PCYsg-hS-p2)
  • Have you written new tests for your changes?
  • Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
  • Have you checked for TypeScript, React or other console errors?
  • Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
  • Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
    • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
  • For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

@southp southp added [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. Storage Addon labels Dec 12, 2024
@southp southp requested a review from a team December 12, 2024 08:45
@southp southp self-assigned this Dec 12, 2024
@southp southp requested a review from jeyip December 12, 2024 08:45
@matticbot
Copy link
Contributor

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

  • blaze-dashboard
  • notifications
  • odyssey-stats

To test WordPress.com changes, run install-plugin.sh $pluginSlug cleanup/remove-storage-addon-config-flag on your sandbox.

@matticbot
Copy link
Contributor

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

Sections (~207 bytes removed 📉 [gzipped])

name                  parsed_size           gzip_size
update-design-flow         -185 B  (-0.0%)      -76 B  (-0.0%)
site-overview              -185 B  (-0.0%)      -65 B  (-0.0%)
plugins                    -185 B  (-0.0%)      -76 B  (-0.0%)
plans                      -185 B  (-0.0%)      -76 B  (-0.0%)
link-in-bio-tld-flow       -185 B  (-0.0%)      -76 B  (-0.0%)
jetpack-app                -185 B  (-0.0%)      -76 B  (-0.1%)
hosting                    -185 B  (-0.0%)      -65 B  (-0.0%)
add-ons                    -185 B  (-0.1%)      -66 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 (~76 bytes removed 📉 [gzipped])

name                                             parsed_size           gzip_size
async-load-signup-steps-plans-theme-preselected       -185 B  (-0.0%)      -76 B  (-0.1%)
async-load-signup-steps-plans                         -185 B  (-0.0%)      -76 B  (-0.1%)

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.

@southp southp merged commit 0b73b81 into trunk Dec 16, 2024
15 checks passed
@southp southp deleted the cleanup/remove-storage-addon-config-flag branch December 16, 2024 06:08
@github-actions github-actions bot removed the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants