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
[COT] Propose ways for plugins and extensions to declare compatibility with custom order tables. #32920
Comments
We should also look into ways for plugins to find out whether a feature is implemented or not, and then plugins should have ways to declare support for particular feature. |
For this you could implement something like Such as: Just a thought. |
Proposal: p7bje6-4kh-p2 |
@Konamiman This one could be closed? |
Yes, as we implemented the features engine already. |
@Konamiman @rrennick Hi, Just wondering what the solution is here. It's mentioned that the feature has been implemented, but no mention of how plugin developers should actually declare compatibility. |
@rrennick Thanks for that link. It's much appreciated |
When we rollout, all plugins and extensions will not be compatible with custom order tables, and we should display this to the merchant if they enable COT for a painless experience.
This could be a filter that extensions can use to declare compatibility, or this could be a plugin header field. Note that we may eventually roll our custom tables for products, customers and other entities, so ideally solution here should be extensible to these future enhancements as well.
The text was updated successfully, but these errors were encountered: