6fb43ed8cb
* Transform object for woocommerce_price_filter legacy widget to be replaced with block alternative * Filter products by price transform * Price Filter formatting * Set set_filterable_product_data data on the widgets screen * Prevent rendering the Price Filter block if there are no products to filter * Prevent Classic Price Filter Widget from being available as a widget * Transform layered nav classic widget to attribute filter block * Allow Filter Products by Stock block to be added as a widget * Allow Active Filters widget to be transformed to Active Filters block * Set showFilterButton to true and showInputFields to false in the transform of Price Filter to minic widgets more * Change displayStyle property to be display_type instead of incorrectly using title * mock @woocommerce/settings for has_filterable_products setting * try: add All Products block to render that filter on the front end * Revert "try: add All Products block to render that filter on the front end" This reverts commit 5ad09e964b77e5c6499b4134cf58d7a6c226424d. * try: add all product block to bypass has_filterable_products check * fix: backend e2e test for attribute filter Co-authored-by: Tung Du <dinhtungdu@gmail.com> |
||
|---|---|---|
| .. | ||
| active-filters | ||
| attribute-filter | ||
| cart | ||
| cart-checkout-shared | ||
| checkout | ||
| classic-template | ||
| featured-category | ||
| featured-product | ||
| handpicked-products | ||
| mini-cart | ||
| price-filter | ||
| product-best-sellers | ||
| product-categories | ||
| product-category | ||
| product-new | ||
| product-on-sale | ||
| product-search | ||
| product-tag | ||
| product-top-rated | ||
| products | ||
| products-by-attribute | ||
| reviews | ||
| single-product | ||
| stock-filter | ||
| README.md | ||
README.md
Blocks
Our blocks are generally made up of up to 4 files:
|- block.js
|- editor.scss
|- index.js
|- style.scss
The only required file is index.js, this sets up the block using registerBlockType. Each block has edit and save functions.
The scss files are split so that things in style are added to the editor and frontend, while styles in editor are only added to the editor. Most of our blocks should use core components that won't need CSS though.
Editing
A simple edit function can live in index.js, but most blocks are a little more complicated, so the edit function instead returns a Block component, which lives in block.js. By using a component, we can use React lifecycle methods to fetch data or save state.
The Newest Products block is a good example to read over, this is a simple block that fetches the products and renders them using the ProductPreview component.
We include settings in the sidebar, called the Inspector in gutenberg. See an example of this.
Other blocks have the concept of an "edit state", like when you need to pick a product in the Featured Product block, or pick a category in the Products by Category block.