Chart Library: Add Grid

[annacmc]

Proposed changes:

This PR introduces a new grid control component

Changes Made:

Dependencies:

• Added @visx/grid to dependencies.

Component:

• Created a new grid control component

Storybook:

• Adds a new storybook + stories to demonstrate usage of grid
• Adds the new grid component to the barchart and makes it available on all

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

Testing instructions:

• Run pnpm install as dependencies have been added

• In your Jetpack local env, navigate to the Storybook development environment:

  pnpm i
  cd projects/js-packages/storybook
  pnpm run storybook:dev
  

• Find JS Packages/Charts/Grid Control in the sidebar

• Verify the grids:

  • Renders correctly with sample data
  • Responds to different data sets via Storybook controls x,y,xy, and none

• Find JS Packages/Charts/Bar Chart in the sidebar

  • check the bar chart renders with the new grid controls

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WordPress.com Simple site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin, and enable the add/charts-library-grids branch.

  • For jetpack-mu-wpcom changes, also add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php file.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack add/charts-library-grids
  

  bin/jetpack-downloader test jetpack-mu-wpcom-plugin add/charts-library-grids
  

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• 🔴 Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

[annacmc]

Temporary any types were added to the grid control scale props with TODO comments, addressing type conflicts between ScaleBand (bar charts) and ScaleLinear (line charts) in visx.

Our previous approaches, including specific scale types, union types, and generic D3Scale types, either restricted reusability, caused further conflicts, or introduced unnecessary dependencies.

This interim solution (any types) ensures flexibility across chart types while deferring a more type-safe implementation to future iterations.

[grzegorz-cp]

👍