23b175d246
* prefersCollection controls shipping visibility * Remove log * Create skeleton pickup options block based on shipping methods * Filter locations to local pickup methods * Correct case of block name * Location styling * Pull pickup details from new core fields * Fix linting warnings on new types * Remove blocks_local_pickup check (this does not exist yet) * Move enable_local_pickup_without_address so it works under all contexts * Fix display of FREE when there are a mix of prices * Remove undefined return value * Update block descriptions * fix message * Correct case Co-authored-by: Nadir Seghir <nadir.seghir@gmail.com> |
||
---|---|---|
.. | ||
active-filters | ||
attribute-filter | ||
cart | ||
cart-checkout-shared | ||
checkout | ||
classic-template | ||
customer-account | ||
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 | ||
shared/styles | ||
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.