A4A > Marketplace: Implement placeholder for term pricing for Hosting, Products & Cart

[yashwin]

Part of https://linear.app/a8c/issue/A4A-1926/marketplace-show-monthlyearly-pricing-for-hosting-and-products

Resolves https://linear.app/a8c/issue/A4A-1929/products-display-monthlyyearly-pricing-on-cards
Resolves https://linear.app/a8c/issue/A4A-1930/hosting-display-monthlyyearly-pricing-on-cards
Resolves https://linear.app/a8c/issue/A4A-1961/cart-display-monthlyyearly-pricing

Proposed Changes

This PR implements a placeholder for term pricing for Hosting, Products & Cart.

Why are these changes being made?

• To support term pricing on A4A Marketplace

Testing Instructions

• Open the A4A live link >
• Test all the scenarios mentioned below > Verify the prices match production.

1. Marketplace > Hosting > Standard Agency Hosting > Refer mode on/off
2. Marketplace > Hosting > Premier Agency Hosting > Refer mode on/off
3. Marketplace > Products > Refer mode on/off

• Append the URL with ?flags=a4a-bd-checkout > Test all the scenarios mentioned below > Verify the UI looks as displayed below with a placeholder for yearly and monthly billing.

Billing term: Monthly

1. Marketplace > Hosting > Standard Agency Hosting > Refer mode off

2. Marketplace > Hosting > Standard Agency Hosting > Refer mode on

3. Marketplace > Hosting > Premier Agency Hosting > Refer mode on

4. Marketplace > Hosting > Premier Agency Hosting > Refer mode off

5. Marketplace > Products > Refer mode off

6. Marketplace > Products > Refer mode on

7. Cart > Refer mode off

8. Cart > Refer mode on

Billing term: Yearly

1. Marketplace > Hosting > Standard Agency Hosting > Refer mode off

2. Marketplace > Hosting > Standard Agency Hosting > Refer mode on

3. Marketplace > Hosting > Premier Agency Hosting > Refer mode off

4. Marketplace > Hosting > Premier Agency Hosting > Refer mode on

5. Marketplace > Products > Refer mode off

6. Marketplace > Products > Refer mode on

7. Cart > Refer mode off

8. Cart > Refer mode on

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 tested accessibility for your changes? Ensure the feature remains usable with various user agents (e.g., browsers), interfaces (e.g., keyboard navigation), and assistive technologies (e.g., screen readers) (PCYsg-S3g-p2).
• 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)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-166058

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-166058&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-166058&env=a8c-for-agencies

Dashboard live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-166058&env=dashboard

[matticbot]

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

Sections (~727 bytes added 📈 [gzipped])

Details

name                          parsed_size           gzip_size
a8c-for-agencies-marketplace      +2060 B  (+0.1%)     +520 B  (+0.1%)
a8c-for-agencies-client           +1072 B  (+0.0%)     +207 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.

[jkguidaven]

@yashwin, I tested it, and it works just fine.

My main concern is that we are doing a lot of conditional rendering. Do you think we can just calculate the value (discount and actual cost) within getProductPricingInfo so we have fewer changes on the rendering logic?

[jkguidaven]

I can see that we are doing conditional rendering with the prices based on the term selected. I wonder if we could just handle the calculation from getProductPricingInfo so we don't have to do conditional rendering here and other places. wdyt?

[yashwin]

Thanks for the review, @jkguidaven!

I have made the changes as per your suggestions. Could you please take another look?

[matticbot]

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 update/a4a/marketplace/implement-term-pricing-for-products-and-hosting on your sandbox.