-
Notifications
You must be signed in to change notification settings - Fork 10.8k
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
Add sync and usage flags to legacy features. #39537
Conversation
Test Results SummaryCommit SHA: ebe26b7
To view the full API test report, click here. To view the full E2E test report, click here. To view all test reports, visit the WooCommerce Test Reports Dashboard. |
Hi @jorgeatorres, Apart from reviewing the code changes, please make sure to review the testing instructions as well. You can follow this guide to find out what good testing instructions should look like: |
FWIW, I've expanded the testing instructions above to add a more clear picture of what's happening. |
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.
LGTM. I've tested that the warning appears on trunk
for Stripe (despite its declaration of compatibility) and that updating to this branch makes the warning go away.
Also tested that enabling/disabling HPOS from the WC > Settings > Advanced > Features screen works correctly.
* Add sync and usage flags to legacy features. * Use transient instead of constant. * Add unit test and changelog. * Add more robustness to unit test by adding more setting values. * PHPCS fixes --------- Co-authored-by: Jorge Torres <jorge.torres@automattic.com>
* Add sync and usage flags to legacy features. (#39537) * Add sync and usage flags to legacy features. * Use transient instead of constant. * Add unit test and changelog. * Add more robustness to unit test by adding more setting values. * PHPCS fixes --------- Co-authored-by: Jorge Torres <jorge.torres@automattic.com> * Prep for cherry pick 39537 --------- Co-authored-by: Vedanshu Jain <vedanshu.jain.2012@gmail.com> Co-authored-by: Jorge Torres <jorge.torres@automattic.com> Co-authored-by: WooCommerce Bot <no-reply@woocommerce.com>
* Add sync and usage flags to legacy features. * Use transient instead of constant. * Add unit test and changelog. * Add more robustness to unit test by adding more setting values. * PHPCS fixes --------- Co-authored-by: Jorge Torres <jorge.torres@automattic.com>
Submission Review Guidelines:
Changes proposed in this Pull Request:
Add the sync and custom table usage enabled flag to legacy so that it does not generate warnings when no compatibility is declared explicitly. The compatibility is taken cared by the
custom_order_tables
flag and so checking for these new feature flags is not required.How to test the changes in this Pull Request:
Using the WooCommerce Testing Instructions Guide, include your detailed testing instructions:
trunk
.wp-admin/plugins.php?plugin_status=incompatible_with_feature
and confirm that the Stripe gateway is listed as incompatible (despite it being compatible). In particular, you'll see that it is listed as incompatible with COT but also a''
feature:wp-admin/plugins.php?plugin_status=incompatible_with_feature
should no longer indicate that Stripe is incompatible with COT.Changelog entry
Significance
Type
Message
Comment