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

Storage Add On: Allow higher term cart item to be added via query param #98899

Open
wants to merge 2 commits into
base: trunk
Choose a base branch
from

Conversation

ddc22
Copy link
Contributor

@ddc22 ddc22 commented Jan 24, 2025

Proposed Changes

  • Allow addition of storage of higher tiers via query param from landing pages

Why are these changes being made?

  • Allow landing pages to directly add storage addons to the cart

Testing Instructions

  • Go to /start/business/?ref=pricing-lp&storage=400gb-storage-add-on
  • Select domain
  • Make sure the 400gb add on is added to the card
  • Also should work with any of these variations
    • 400gb-storage-add-on
    • 350gb-storage-add-on
    • 300gb-storage-add-on
    • 250gb-storage-add-on
    • 200gb-storage-add-on
    • 150gb-storage-add-on
    • 100gb-storage-add-on
image

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)?

@matticbot
Copy link
Contributor

matticbot commented Jan 24, 2025

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

Sections (~848 bytes added 📈 [gzipped])

name                     parsed_size           gzip_size
theme                         +172 B  (+0.0%)      +76 B  (+0.0%)
tailored-ecommerce-flow       +172 B  (+2.5%)      +67 B  (+2.9%)
stats                         +172 B  (+0.0%)      +64 B  (+0.0%)
site-purchases                +172 B  (+0.0%)      +65 B  (+0.0%)
site-overview                 +172 B  (+0.0%)      +68 B  (+0.0%)
purchases                     +172 B  (+0.0%)      +65 B  (+0.0%)
posts-custom                  +172 B  (+0.0%)      +65 B  (+0.0%)
posts                         +172 B  (+0.0%)      +65 B  (+0.0%)
plugins                       +172 B  (+0.0%)      +63 B  (+0.0%)
plans                         +172 B  (+0.0%)      +77 B  (+0.0%)
migrate                       +172 B  (+0.0%)      +62 B  (+0.1%)
jetpack-app                   +172 B  (+0.0%)      +70 B  (+0.1%)
import-hosted-site-flow       +172 B  (+0.0%)      +82 B  (+0.0%)
hosting                       +172 B  (+0.0%)      +65 B  (+0.0%)
domains                       +172 B  (+0.0%)      +65 B  (+0.0%)
checkout                      +172 B  (+0.0%)      +65 B  (+0.0%)
add-ons                       +172 B  (+0.0%)      +65 B  (+0.1%)
update-design-flow             -48 B  (-0.0%)      +24 B  (+0.0%)
signup                         -48 B  (-0.0%)      +24 B  (+0.0%)
link-in-bio-tld-flow           -48 B  (-0.0%)      +24 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.

Async-loaded Components (~65 bytes added 📈 [gzipped])

name                      parsed_size           gzip_size
async-load-design-blocks       +172 B  (+0.0%)      +65 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.

@matticbot
Copy link
Contributor

matticbot commented Jan 24, 2025

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

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

  • help-center
  • notifications
  • wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug add/storage-add-on-definition on your sandbox.

@ddc22 ddc22 self-assigned this Jan 24, 2025
@ddc22 ddc22 requested review from aneeshd16 and a team January 24, 2025 17:11
@matticbot matticbot added the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Jan 24, 2025
@ddc22 ddc22 marked this pull request as ready for review January 24, 2025 17:11
add_on_slug: AddOns.ADD_ON_100GB_STORAGE,
} );
break;
if ( STORAGE_ADD_ONS.includes( selectedStorage ) ) {
Copy link
Contributor

Choose a reason for hiding this comment

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

The add on slug -> quantity mapping is already defined here:

export const getAddOnsList = (): AddOnMeta[] => {

Can we use that instead of redefining it? Also, can we preserve the Tracks event? 🙂

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Nice catch on the event and I will use the tracks event

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. Storage Addon
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants