-
Notifications
You must be signed in to change notification settings - Fork 219
move legacy payment processing to its own class #6519
Conversation
Size Change: 0 B Total Size: 862 kB ℹ️ View Unchanged
|
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.
I tested and it works thanks!
Approving so you can merge if you don't agree about changing the class name.
/** | ||
* Legacy class. | ||
*/ | ||
class Legacy { |
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.
Do you think Legacy
on its own is an OK name? Do we plan to put other stuff here, or would LegacyPayments
be better and more descriptive?
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.
@wavvves and I discussed this when we worked on it in our pairing session, for now we can keep it Legacy but if it turns out to be too big we will split it down.
* Empty commit for release pull request * Add changelog for the 7.8.0 release * Add testing notes for 7.8.0 release * move legacy payment processing to its own class (#6519) * update changelog and testing instructions after the cherry-pick * add link * Featured Item: Fix colors from default palette not being applied (#6525) Gutenberg uses two different attributes for text colors: * `style.color.text`, and * `textColor` However, the second one is used only when a color from the default palette is selected AND the post is saved and reloaded. With this fix we use the human readable string from the default palette as a CSS variable. Please note that while Gutenberg correctly assigns the appropriate CSS class to render the right color, the problem is that if the color is handled by a class, it can be overridden for example by themes. See #6492 * upload new zip * update changelog * Revert "Remove Combobox patch (#6465)" (#6531) This reverts commit 617f297. * upload new zip * Bumping version strings to new version. Co-authored-by: github-actions <[email protected]> Co-authored-by: Luigi <[email protected]> Co-authored-by: Seghir Nadir <[email protected]> Co-authored-by: Lucio Giannotta <[email protected]> Co-authored-by: Albert Juhé Lluveras <[email protected]>
* Empty commit for release pull request * Add changelog for the 7.8.0 release * Add testing notes for 7.8.0 release * move legacy payment processing to its own class (#6519) * update changelog and testing instructions after the cherry-pick * add link * Featured Item: Fix colors from default palette not being applied (#6525) Gutenberg uses two different attributes for text colors: * `style.color.text`, and * `textColor` However, the second one is used only when a color from the default palette is selected AND the post is saved and reloaded. With this fix we use the human readable string from the default palette as a CSS variable. Please note that while Gutenberg correctly assigns the appropriate CSS class to render the right color, the problem is that if the color is handled by a class, it can be overridden for example by themes. See #6492 * upload new zip * update changelog * Revert "Remove Combobox patch (#6465)" (#6531) This reverts commit 617f297. * upload new zip * Bumping version strings to new version. * Fix MD lint errors and fix conflicts * Empty commit for release pull request * Release: 7.8.3 (#6602) * Fix PHP notice in Mini Cart when prices included taxes (#6537) * Empty commit for release pull request * Add changelog to readme.txt * Update versions * Add Testing steps for version 7.8.1 * Bumping version strings to new version. * Empty commit for release pull request * Empty commit for release pull request * Replace instances of wp_is_block_theme() with wc_current_theme_is_fse_theme() (#6590) * update changelog and testing instructions * Empty commit for release pull request * upload zip * Bumping version strings to new version. * Fix images hidden by default in Product grid blocks (#6599) * update changelog and testing instructons * Bumping version strings to new version. Co-authored-by: Albert Juhé Lluveras <[email protected]> Co-authored-by: github-actions <[email protected]> Co-authored-by: Luigi <[email protected]> * fix MD lint errors * fix sort deps Co-authored-by: github-actions <[email protected]> Co-authored-by: Seghir Nadir <[email protected]> Co-authored-by: Lucio Giannotta <[email protected]> Co-authored-by: Albert Juhé Lluveras <[email protected]> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
When moving Store API out of WooCommerce blocks, we forget to pull out a specific function that handled legacy payment methods that didn't explicitly integrate with Store API and Checkout block, that code was living along side other payment related code that is meant for Checkout.
In this PR, I separate both of them so Checkout related code is still behind a feature flag, and payment handling code for Store API is not.
Testing
WooCommerce Visibility
Changelog