Uses TLD to check for subdomain status for Mapping

[StevenPartridge]

rather than a hardcoded list of TLDs on the Front End

relies on wpcom diff: 170938-ghe-Automattic/wpcom

Related to # https://github.com/Automattic/nomado-issues/issues/947

Proposed Changes

• Uses the already called 'domain-mapping-info' API call, and a new key added to that, to get the TLD from the backend (Single Source of Truth), instead of relying purely on a simple check on the front end (incomplete second source of truth).
• Introduces optional parameter, 'tld' to the isSubdomain function
• If 'tld' is provided and validated, uses that TLD or SLD to safely check if the domain is using an SLD or just a subdomain
• Leaves the original functionality to ensure nothing breaks unexpectedly, but it would be good to get the TLD from the backend in all cases where isSubdomain is used, to keep it as Single Source of Truth

Why are these changes being made?

• When users connect domains, we suggest some guidance based on whether it's a Subdomain or a full Domain (possibly with multi-level TLD). Users have expressed confusion and reached out to HEs for assistance when provided the wrong guidance
• The current check only looks at a list of hard-coded SLDs in the front-end (which is technically how the backend works, but that should be the source of truth as it's MASSIVELY more complete)
• Instead of adding a few SLDs to that list at a time (won't solve everything), or adding the entire list (too big), Kamen suggested this exact approach on Slack
  • p1736980903062009-slack-C0BNMNMNG

Testing Instructions

• Load this branch and proxy Sandbox with 170938-ghe-Automattic/wpcom
• Open the network tab, using the filter mapping-setup-info to isolate the single API call
• You can skip actually mapping a thing and go straight to the correct Step
• Load up /domains/mapping/YOURSITE.tld/setup/notsubdomain.ca?firstVisit=true Replace YOURISTE.tld with a test site
• Test with a series of domains, subdomains, and two level TLDs, deeply nested subdomains, etc.
  • notsubdomain.ca (ca)
  • subdomain.domain.ca (ca)
  • domain.qc.ca (qc.ca)
  • subdomain.domain.qc.ca (qc.ca)
  • more.
  • I've been testing with a domain provided by an HE as well, a full example I used: http://calypso.localhost:3000/domains/mapping/nomado-test-sp-2025-01-13.blog/setup/assnat.qc.ca?firstVisit=true

With fix (assnat.qc.ca localhost):

Without fix (assnat.qc.ca on wordpress.com):

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:commit-d4b1370026901f8d84dda3f09e4f5757d3bdaa2d

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

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

[matticbot]

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

Sections (~334 bytes added 📈 [gzipped])

name                  parsed_size           gzip_size
update-design-flow         +370 B  (+0.0%)     +119 B  (+0.0%)
link-in-bio-tld-flow       +370 B  (+0.0%)     +119 B  (+0.0%)
domains                    +370 B  (+0.0%)     +116 B  (+0.0%)
copy-site-flow             +370 B  (+0.0%)     +119 B  (+0.0%)
hosting                    +327 B  (+0.0%)     +105 B  (+0.0%)
plans                      +318 B  (+0.0%)     +101 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 (~229 bytes added 📈 [gzipped])

name                                                      parsed_size           gzip_size
async-load-signup-steps-domains                                +370 B  (+0.1%)     +119 B  (+0.1%)
async-load-calypso-my-sites-current-site-domain-warnings       +318 B  (+1.0%)     +110 B  (+1.5%)

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.