-
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
Add-ons: Storage as a tiered-volume product [WIP] #75294
base: trunk
Are you sure you want to change the base?
Conversation
…r conditional rendering.
…to redux/global state
…additional parameters.
… revisit these, and likely use more of the already existing selectors. But this works for now/testing
This PR modifies the release build for happy-blocks To test your changes on WordPress.com, run To deploy your changes after merging, see the documentation: PCYsg-r7r-p2 |
This PR modifies the release build for editing-toolkit To test your changes on WordPress.com, run To deploy your changes after merging, see the documentation: PCYsg-mMA-p2 |
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: App Entrypoints (~295 bytes removed 📉 [gzipped])
Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used. Sections (~910 bytes removed 📉 [gzipped])
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 (~561 bytes removed 📉 [gzipped])
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. 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.
I know this is a WIP but I had a drive-by suggestion.
const selectedSite = useSelector( getSelectedSite ); | ||
|
||
return ( addOnSlug: string, quantity?: number ): string => { | ||
const checkoutLinkFormat = `/checkout/${ selectedSite?.slug }/${ addOnSlug }`; |
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.
If selectedSite
does not exist, this will create a URL like /checkout/undefined/product
. Do you think we should do something different in that case? Maybe just /checkout/product
(which should work well by showing a site picker first).
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! I added a check for this now, and it will return the site picker if no selectedSite
is provided.
…eless checkout link
…wn field to choose the wanted variation (e.g. a price tier, quantity, etc.)
Related to #
Proposed Changes
getPriceTierForUnits
.To do
Testing Instructions
Pre-merge Checklist