-
Notifications
You must be signed in to change notification settings - Fork 835
Forms: Try intergration api #45258
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: trunk
Are you sure you want to change the base?
Forms: Try intergration api #45258
Conversation
Introduces a centralized Integrations registry for managing form integrations, moving MailPoet integration registration from a hardcoded array to dynamic registration via the new registry. Updates initialization logic, refactors tests, and adds dedicated unit tests for the Integrations registry.
Introduces a new Integration class to encapsulate integration data. Updates Integrations::register to accept either an Integration object or array, improving flexibility. Refactors MailPoet integration registration to use the new class. Adds comprehensive unit tests for Integration and Integrations registration, including object and array handling.
Extracts inline integration components from the IntegrationsModal into separate, reusable component files. This improves code organization, maintainability, and allows for better reusability across the application. Changes: - Created ServiceIntegrationCard component for service integrations with form-specific settings support - Created PluginIntegrationCard component for plugin integrations with full state management - Updated IntegrationsModal to use hybrid approach with specific cards for known integrations and generic cards for new ones - Updated dashboard integrations to use the same hybrid pattern - Refactored both modal and dashboard to use dynamic mapping instead of hardcoded individual cards - Added proper TypeScript interfaces for component props - Maintained backward compatibility with existing specific integration components 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
Are you an Automattician? The PR will need to be tested on WordPress.com. This comment will be updated with testing instructions as soon the build is complete. |
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! |
Code Coverage SummaryCoverage changed in 4 files.
6 files are newly checked for coverage. Only the first 5 are listed here.
Full summary · PHP report · JS report If appropriate, add one of these labels to override the failing coverage check:
Covered by non-unit tests
|
All integration to be extended via an
Proposed changes:
Other information:
Jetpack product discussion
Does this pull request change what data or activity we track or use?
Testing instructions:
Visit the dashboard to make see the new dummy intergreation.