Reading Settings: Rename 'Default posts page' default option to 'None'

[mashikag]

Proposed Changes

• Rename 'Default posts page' default option to 'None'

Testing Instructions

• Go to http://calypso.localhost:3000/settings/reading/$site
• Ensure the default option displays "None" instead of "Select"
  

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

Fixes #72603

[github-actions]

Calypso Live (direct link)

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

Jetpack Cloud live (direct link)

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

[matticbot]

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

Sections (~76 bytes added 📈 [gzipped])

name              parsed_size           gzip_size
settings-reading       +234 B  (+0.1%)      +76 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.

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.

[ivan-ottinger]

Looks and works as expected. 🙂👍🏼

One thing we should consider though is the translation. If we are launching next week, the translation of the new string won't be ready:

Because of that we can consider adding conditional that will display the old string until the new one is ready. Example: 2ee9f-pb - video at 1:30 timestamp.

[mashikag]

Great point @ivan-ottinger, and thank you for pointing me to the learning source too (I have bookmarked it ♥️)!

[ivan-ottinger]

Great point @ivan-ottinger, and thank you for pointing me to the learning source too (I have bookmarked it ♥️)!

My pleasure! 🙂

Code looks good and works as expected - tested with English and Spanish locales.

English displays the "new" —— None —— string, Spanish displays the "old" (already translated) —— Select —— string.

I did not observe any regression nor errors / warnings. Tested with Simple, Atomic and Jetpack self-hosted site.

[a8ci18n]

This Pull Request is now available for translation here: https://translate.wordpress.com/deliverables/7787479

Thank you @mashikag for including a screenshot in the description! This is really helpful for our translators.

[a8ci18n]

Translation for this Pull Request has now been finished.