-
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
Tracking issue: Adding directives to WooCommerce blocks #42486
Comments
EDIT: the PR was moved to woocommerce/woocommerce-blocks#8220. This is now the one to be reviewed. |
I've made some progress with the experiment and recorded a video showing how the simple price filter block behaves now. You can see it in the PR description. |
Let's try using |
Let's try using |
I've added a link to an experiment that shows how to use the Interactivity API for filters with multiple product query blocks. Remember that it's still WIP 🚧, as it depends on WordPress/block-interactivity-experiments#139 to be finished and merged. I'll work on documenting everything as well once the code is ready. |
I've started working on replacing all the Also, I've updated both demos to use these changes, so now directives start with |
BTW, I forgot to mention that the Stackblitz - Interactivity API demo: filters with multiple product queries demo is working now. I still have to document it, but you can take a look at the code already if you want. 😄 |
Another update:
|
Quick update: The changes for the directives prefix have been recently merged: The PR that adds store serialization and hydration (among other things) is ready to review: |
Forgot to mention that I also updated woocommerce/woocommerce-blocks#8221 (the Simple Price Filter demo) with the latest changes in woocommerce/woocommerce-blocks#8447. 🙂 |
Sorry for the long silence here. 😅 A while ago, I started working on woocommerce/woocommerce-blocks#8524 to make the Filter blocks start using the Interactivity API, which will close issue woocommerce/woocommerce-blocks#8456. It got stale because it depended on WordPress/block-interactivity-experiments#163, which is already implemented and merged. I'll move those changes to woocommerce/woocommerce-blocks#8524 and continue working on the remaining tasks there. 🙂 |
I've finished updating the Interactivity API code inside WooCommerce blocks. This is the PR for these changes, ready for review. I also created a new PR for the Simple Price Filter block, showcasing how to use the updated Interactivity API in blocks. The old one is closed. |
I've opened a PR implementing server-side-rendered updates for interactive regions during client-side navigation.
I also updated the Tracking Issue description to reflect the current status. |
The Woo team has started working on the Filter blocks and created their own Epic: I decided to close the related issue and PR we created a while ago, as the work there was unfinished. |
Heads up, we have started working on the new |
I forgot to announce that the new Interactivity Now, the Frontend Filters improvements can benefit from these changes. 😊 |
This aims to be the tracking issue to follow the progress of including the Interactivity API in some WooCommerce blocks, especially the Product block. As WooCommerce blocks could potentially benefit from this new API, we want to understand what is needed in order to implement some of the blocks using it.
Note that the mentioned API will ideally be included in Gutenberg and WordPress core at some point. However, to start experimenting as soon as possible, we are moving the needed scripts into the repo so we can start testing the API now.
Experiments
Done
data-woo-
woocommerce-blocks#8316afterLoad
callbacks tostore()
function woocommerce-blocks#10338store()
API woocommerce-blocks#11065In progress
Next
The text was updated successfully, but these errors were encountered: