Skip to content
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

Merged
merged 5 commits into from
Aug 2, 2023
Merged

Conversation

vedanshujain
Copy link
Contributor

@vedanshujain vedanshujain commented Aug 2, 2023

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:

  1. Check out trunk.
  2. Enable a plugin that has declared compatibility with HPOS. For example, the WooCommerce Stripe gateway.
  3. You should be seeing the incompatibility warning on all admin screens:
    Screenshot 2023-08-02 at 14 10 52
  4. Go to 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:
    Screenshot 2023-08-02 at 14 08 01
  5. Check out this branch and refresh the page.
  6. The warning should now be gone.
  7. The list of plugins on wp-admin/plugins.php?plugin_status=incompatible_with_feature should no longer indicate that Stripe is incompatible with COT.

Changelog entry

  • Automatically create a changelog entry from the details below.

Significance

  • Patch
  • Minor
  • Major

Type

  • Fix - Fixes an existing bug
  • Add - Adds functionality
  • Update - Update existing functionality
  • Dev - Development related task
  • Tweak - A minor adjustment to the codebase
  • Performance - Address performance issues
  • Enhancement - Improvement to existing functionality

Message

Comment

@github-actions github-actions bot added the plugin: woocommerce Issues related to the WooCommerce Core plugin. label Aug 2, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Aug 2, 2023

Test Results Summary

Commit SHA: ebe26b7

Test 🧪Passed ✅Failed 🚨Broken 🚧Skipped ⏭️Unknown ❔Total 📊Duration ⏱️
API Tests25900202611m 8s
E2E Tests1890019020818m 27s

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.

@vedanshujain vedanshujain marked this pull request as ready for review August 2, 2023 14:38
@jorgeatorres jorgeatorres self-requested a review August 2, 2023 15:29
@github-actions
Copy link
Contributor

github-actions bot commented Aug 2, 2023

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:
https://github.com/woocommerce/woocommerce/wiki/Writing-high-quality-testing-instructions

@jorgeatorres
Copy link
Member

FWIW, I've expanded the testing instructions above to add a more clear picture of what's happening.

Copy link
Member

@jorgeatorres jorgeatorres left a 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.

@jorgeatorres jorgeatorres added the needs: analysis Indicates if the PR requires a PR testing scrub session. label Aug 2, 2023
@lanej0 lanej0 added needs: external testing Indicates if the PR requires further testing conducted by testers external to the development team. and removed needs: analysis Indicates if the PR requires a PR testing scrub session. labels Aug 2, 2023
@lanej0 lanej0 merged commit 8cf7377 into trunk Aug 2, 2023
29 checks passed
@lanej0 lanej0 deleted the fix/incompat-warning branch August 2, 2023 17:38
@github-actions github-actions bot added this to the 8.1.0 milestone Aug 2, 2023
@github-actions github-actions bot added the needs: analysis Indicates if the PR requires a PR testing scrub session. label Aug 2, 2023
@jonathansadowski jonathansadowski modified the milestones: 8.1.0, 8.0.0 Aug 2, 2023
github-actions bot pushed a commit that referenced this pull request Aug 2, 2023
* 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>
jonathansadowski pushed a commit that referenced this pull request Aug 2, 2023
* 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>
@lanej0 lanej0 removed the needs: analysis Indicates if the PR requires a PR testing scrub session. label Aug 2, 2023
tommyshellberg pushed a commit that referenced this pull request Aug 7, 2023
* 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>
@nigeljamesstevenson nigeljamesstevenson added the status: analysis complete Indicates if a PR has been analysed by Solaris label Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs: external testing Indicates if the PR requires further testing conducted by testers external to the development team. plugin: woocommerce Issues related to the WooCommerce Core plugin. status: analysis complete Indicates if a PR has been analysed by Solaris
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants