Hello and welcome to another round of Snaps from the WooCommerce Store Editing team! 🎇
Every couple of weeks, we give an update on all the work being done on WooCommerce Blocks from behind the scenes.
Let’s take a look at some highlights of what we’ve done since our last update.
Note that the linked #numbers that accompany each item below point to the relevant issues and pull requests on the GitHub repository.
What We’re Working On 🚧
We’ve worked on a number of things in the last two weeks but here are some specific items we want to highlight.
Product Collection Block
This project aims to create a Product Collection block with the functionality of Products (Beta) block but as an improved experience for displaying your products. It includes foundational work to cover the current Products block functionalities, improvements around Inspector Controls, and a set of basic patterns for a new block.
We’re currently working on new features and further improvements that will allow for even easier store set up.
Return to top after page change (#43817)
Some time ago, we introduced client-side navigation to the Product Collection block meaning there’s no page reload when changing pages. We received feedback that the block should scroll to the top after page change and here’s our response! We kicked off this work and it should be ready soon.
Fix incorrect product data displayed in Product Collection in context of Single Product block (#44123)
We’re putting a lot of effort to make Product Collection your go-to block in terms of product presentation. There was an issue in the Editor that if you placed a Product Collection block inside a Single Product block, it would display some data inherited from the Single Product block. It could’ve discouraged you from using Product Collection in that place (even though it works fine in the frontend) but we’ve fixed it so you have a better Editor experience!
| Before | After |
|---|---|
 |  |
Templating logic update
We are making some improvements to the logic that handles WooCommerce templates, those are Product Catalog, Products by Category, Single Product, Cart, Checkout… The goal of this project is to improve test coverage, modernize the code and, with it, fix some long-standing bugs which affect some edge cases.
Avoid duplicate templates appearing on the Site Editor when the WooCommerce template and the theme template have been customized by the user (#44000)
We resolved an issue that might cause duplicate templates to appear in the Site Editor. It required the store to be using a block theme with custom WooCommerce templates and having user customizations for the WooCommerce default template and the theme template. After fixing this, there are no more duplicate templates in the list!
Add e2e tests for theme customization of block templates (#43650, #43778, #43750, #43794 and #43992)
We put a lot of effort into making sure we have test coverage for themes overriding WooCommerce templates. While it might initially look like a straightforward task, the logic is full of exceptions and edge cases: templates which fallback into other templates, the possibility of having customized the WooCommerce templates and/or the theme templates in parallel, etc.
Our test coverage now is much better than it was a few weeks ago, and this should allow us to improve the templating logic with more confidence on not breaking things for existing stores.
Add e2e tests for the Page Wrapper block (#44122)
Continuing the effort on improving our automated testing infrastructure, we added tests to the Page Wrapper block, that’s the block that makes the Cart and Checkout page contents to be visible in the Cart and Checkout templates.
Other Notable PRs / Issues ✅
- Update WC Blocks Playwright tests docs (#43650 and #43779): after the WC Blocks merge into the monorepo, some of the commands which appeared in the docs stopped working. We have now fixed them and updated the docs.
Thanks for following along with us – until next time! 👋
Leave a Reply