99ba060720
* Product Query: add Feedback Prompt in inspector The prompt doesn't appear at the very bottom as there isn't currently any straightforward way to do this in the block variation. More investigation is required. * Product Query: Change icon, description and name * Product Query: switch to Feature plugin flag * Add all currently available atomic blocks to the default Product Query template * Update feature flags doc * Change SKU and Stock Indicator feature flags * Change feature flags docs * Add title prop to the `FeedbackPrompt` and add a title to the Product Query one * Hacky solution to display the feedback block at the bottom The order of the inspector controls is set in Gutenberg. We can hack our way down by hooking to the “color” group and display our feedback there. Other panels would be displayed below that if added, such as borders and margin. * Reduce Product Query default template * Fix e2e tests after Product Query block name change (https://github.com/woocommerce/woocommerce-blocks/pull/7840) * Product Query: Add a better default pattern (https://github.com/woocommerce/woocommerce-blocks/pull/7833) * Product Query: Add a better default pattern * Product Price: Add bottom margin Co-authored-by: Albert Juhé Lluveras <contact@albertjuhe.com> Co-authored-by: Daniel Dudzic <daniel.dudzic@automattic.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.