-
Notifications
You must be signed in to change notification settings - Fork 799
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
packages: Add a bunch of missing deps #37141
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 🤖 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. Once your PR is ready for review, check one last time that all required checks appearing at the bottom of this PR are passing or skipped. 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:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Boost plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Search plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Social plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Starter Plugin plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Protect plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Videopress plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Migration 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:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Automattic For agencies client plugin:
If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests look good, let's give this a try. Did you find all those misses via Phan?
Yes, this is all the result of looking at where Phan complained about undeclared classes. |
The following dependencies are added: * packages/backup: packages/my-jetpack * packages/boost-core: packages/connection * packages/forms: packages/logo, packages/status, packages/sync * packages/import: packages/sync * packages/search: packages/sync * packages/videopress: packages/my-jetpack * packages/yoast-promo: packages/assets Also, the following are added as dev-dependencies and flagged as test-only so they won't result in dependency cycles: * packages/config: 14 different things it can conditionally load * packages/connection: packages/licensing, packages/sync * packages/my-jetpack: packages/search, and mark packages/videopress as test-only too * packages/status: packages/connection, packages/identity-crisis, packages/plans * packages/sync: packages/search, packages/waf Note I haven't fully checked that all these really are test-only with any non-test uses properly checked with `class_exists` or the like. I do note that status→connection is only because of the `Jetpack_Options` class and is _not_ checked, which seems unfortunate and probably should be fixed somehow at some point.
8a1a32a
to
bb03b6a
Compare
"automattic/jetpack-changelogger": "@dev" | ||
"automattic/jetpack-changelogger": "@dev", | ||
"automattic/jetpack-licensing": "@dev", | ||
"automattic/jetpack-sync": "@dev" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it ok that the Connection package requires sync, while the Sync package requires the connection package?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should be ok.
- Composer doesn't care as long as it can come up with a consistent set of packages, which it can.
- Our build scripts are ok with it now as long as at least one of the deps is marked as "test-only", thanks to cli: Allow flagging deps as test-only #37140.
- Is there anything else you're concerned about?
Proposed changes:
The following dependencies are added:
Also, the following are added as dev-dependencies and flagged as test-only so they won't result in dependency cycles:
Note I haven't fully checked that all these really are test-only with any non-test uses properly checked with
class_exists
or the like. I do note that status→connection is only because of theJetpack_Options
class and is not checked, which seems unfortunate and probably should be fixed somehow at some point.Other information:
Jetpack product discussion
None
Does this pull request change what data or activity we track or use?
No
Testing instructions: