Stats: navigate by full periods

[kangzj]

Related to https://github.com/Automattic/jetpack-roadmap/issues/2181 - Partial fix

Proposed Changes

• Navigate by full periods - year, month whenever possible

Why are these changes being made?

• Enhancement

Testing Instructions

• Open Calypso Live
• Choose Month to date
• Click arrows to change date range
• Ensure it changes back/forward by full month
• Try with Year to date
• Ensure similar behaviour by only by years

Screen.Recording.2025-01-31.at.4.41.14.PM.mov

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

[github-actions]

Calypso Live (direct link)

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

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

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

[matticbot]

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

Sections (~222 bytes added 📈 [gzipped])

name                            parsed_size           gzip_size
stats                                +871 B  (+0.1%)     +187 B  (+0.1%)
plugins                               +55 B  (+0.0%)      +19 B  (+0.0%)
media                                 +55 B  (+0.0%)      +19 B  (+0.0%)
jetpack-cloud-agency-dashboard        +55 B  (+0.0%)      +16 B  (+0.0%)
backup                                +55 B  (+0.0%)      +16 B  (+0.0%)
activity                              +55 B  (+0.0%)      +16 B  (+0.0%)
a8c-for-agencies-sites                +55 B  (+0.0%)      +16 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 (~206 bytes added 📈 [gzipped])

name                                               parsed_size           gzip_size
async-load-store-app-store-stats-listview               +871 B  (+0.7%)     +187 B  (+0.6%)
async-load-store-app-store-stats                        +871 B  (+0.3%)     +187 B  (+0.3%)
async-load-design-playground                             +55 B  (+0.0%)      +19 B  (+0.0%)
async-load-design-blocks                                 +55 B  (+0.0%)      +19 B  (+0.0%)
async-load-design                                        +55 B  (+0.0%)      +19 B  (+0.0%)
async-load-calypso-post-editor-media-modal               +55 B  (+0.0%)      +19 B  (+0.0%)
async-load-calypso-post-editor-editor-media-modal        +55 B  (+0.0%)      +19 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]

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

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

• blaze-dashboard
• command-palette-wp-admin
• help-center
• notifications
• odyssey-stats
• whats-new
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug update/full-period-support-arrow-nav on your sandbox.

[dognose24]

👍

[a8ck3n]

This is failing for one specific case for me. If I select year-to-date and the date is Jan 31st, the previous arrow will navigate to Dec (previous month) instead of to 2024 (previous year). I'm thinking this bug would only surface on Jan 31 of any given year though.

[kangzj]

This is failing for one specific case for me. If I select year-to-date and the date is Jan 31st, the previous arrow will navigate to Dec (previous month) instead of to 2024 (previous year). I'm thinking this bug would only surface on Jan 31 of any given year though.

Nice catch! When I tested, it worked. I think it's a problem for how today is compared... again...

Fitted in another fix for momentSiteZone and hopefully this time it will resolve all the related issues around timezones.