71e77e38e0
* Disable apply button when there is no change to selected options More info: https://github.com/woocommerce/woocommerce-blocks/issues/7116 * Add tests to the Filter Attribute block Since we are making changes to the Filter Attributes block to fix issue woocommerce/woocommerce-blocks#7373, we are also adding tests to make sure the changes are providing the expected behavior The setup-globals file was changed to add 'attributes' and 'has_filterable_products' properties to it, so it can be used in the tests. * Merge test utils methods with attribute filter block Removing test utils file and merging the methods with the Attribute Filter block to prevent tests from failing due to Jest configuration that only allow test files to exists inside a 'test' folder * Remove checked.length === 0 condition **Why was this condition needed before?** Because when the user initially load the page, no filter is selected therefore we needed this condition to keep the Apply disabled in this case. **Why we don't need it anymore?** Because now in this PR we add following code: ```jsx const activeFilters = getActiveFilters( attributeObject ); if ( activeFilters.length === checked.length ) { return checked.every( ( value ) => activeFilters.includes( value ) ); } ``` This will return `true` when the user initially loads the page & Apply button will become disabled. Therefore, I believe it's safe to remove `checked.length === 0` condition. More info: https://github.com/woocommerce/woocommerce-blocks/pull/7373#discussion_r994737313 * Add filterSize param to test setup With this configuration, it is now possible to modify the current filter size in order to improve tests Co-authored-by: Alexandre Lara <allexandrelara@gmail.com> |
||
|---|---|---|
| .. | ||
| active-filters | ||
| attribute-filter | ||
| cart | ||
| cart-checkout-shared | ||
| checkout | ||
| classic-template | ||
| featured-items | ||
| filter-wrapper | ||
| handpicked-products | ||
| mini-cart | ||
| price-filter | ||
| product-best-sellers | ||
| product-categories | ||
| product-category | ||
| product-new | ||
| product-on-sale | ||
| product-query | ||
| product-search | ||
| product-tag | ||
| product-top-rated | ||
| products | ||
| products-by-attribute | ||
| rating-filter | ||
| 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.