Components: Remove Jetpack overriding styles#47056
Conversation
|
Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.
Interested in more tips and information?
|
|
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
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 🤖 Follow this PR Review Process:
If you have questions about anything, reach out in #jetpack-developers for guidance! Jetpack plugin: The Jetpack plugin has different release cadences depending on the platform:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Backup plugin: No scheduled milestone found for this plugin. If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Boost plugin: No scheduled milestone found for this plugin. If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Search plugin: No scheduled milestone found for this plugin. If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Social plugin: No scheduled milestone found for this plugin. If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Starter Plugin plugin: No scheduled milestone found for this plugin. If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Protect plugin: No scheduled milestone found for this plugin. If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Videopress plugin: No scheduled milestone found for this plugin. If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Mu Wpcom plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Inspect plugin: No scheduled milestone found for this plugin. If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Wpcomsh plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Automattic For agencies client plugin: No scheduled milestone found for this plugin. If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Classic Theme helper plugin plugin: No scheduled milestone found for this plugin. If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Paypal Payment buttons plugin: No scheduled milestone found for this plugin. If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Wpcloud Sso plugin: No scheduled milestone found for this plugin. If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. |
Code Coverage SummaryCoverage changed in 2 files.
|
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
| @@ -1 +1 @@ | |||
| @use "@automattic/jetpack-base-styles/gutenberg-base-styles" as gb; | |||
There was a problem hiding this comment.
Jetpack Tabs we could look at replacing with @wordpress/ui.Tabs pretty soon.
There was a problem hiding this comment.
That would be the vision across a lot of components
There was a problem hiding this comment.
That's going to be addressed when unifying the header, no?
| import analytics from '@automattic/jetpack-analytics'; | ||
| import { getProductCheckoutUrl } from '@automattic/jetpack-components'; | ||
| import { useConnection } from '@automattic/jetpack-connection'; | ||
| import { ToggleControl } from '@wordpress/components'; |
There was a problem hiding this comment.
Would it make sense to keep one PR in green-colour removals and then separate PR (either merged before this or after) on more substantial component-switcheroo?
Just because this will require more thorough functional testing, vs just visual.
…irectly
Deleted:
- projects/js-packages/components/components/toggle-control/ (entire directory — index.tsx, styles.module.scss, README.md, stories/)
Removed export:
- projects/js-packages/components/index.ts — removed ToggleControl export
Updated 23 consumer files — changed ToggleControl import from @automattic/jetpack-components to @wordpress/components:
- 5 traffic files (seo, related-posts, site-stats, blaze, google-analytics)
- 3 security files (allowList, waf, sso)
- 3 performance files (search, speed-up-site, media)
- 2 newsletter files (subscriptions-settings, newsletter-categories)
- 1 earn file (ads)
- 1 component (module-toggle)
- 3 writing files (writing-media, custom-content-types, comments) — done by subagent
- 2 publicize files (social-image-generator/toggle, utm-toggle)
- 1 CRM file (workflow-row)
- 1 Boost file (module.tsx)
- 1 Protect file (firewall-footer.jsx)
Removed custom props from call sites:
- toggling={...} removed from all direct <ToggleControl> usages (~30 instances across 12 files)
- size="small" removed from Boost and Protect (3 instances)
- Merged duplicate @wordpress/components imports in 2 files
Draft PR, DO NOT MERGE
Fixes #
Proposed changes:
Other information:
Jetpack product discussion
Does this pull request change what data or activity we track or use?
Testing instructions: