435e341fe6
* Scroll to errors when interacting with radio buttons * Fix full stop wrapping in checkout * Make type guard for api response reusable * Merge useShippingData and useSelectShippingRate Overlapping functionality and responsibility easily merged into a single hook. * ShippingDataProvider Typescript * Create errors when receiving errors via thunk * Update DEFAULT_ERROR_MESSAGE * Update tests since all errors are set via new action * Correct SET_ERROR_DATA * Update json error text and allow it to be dismissed * Add back missing comment in types * Put back typedef * Allow Store Notice Containers to display subContexts without changing original context * receiveError handles cart * Update assets/js/data/cart/notify-errors.ts Co-authored-by: Thomas Roberts <5656702+opr@users.noreply.github.com> * Update assets/js/base/context/hooks/shipping/types.ts Co-authored-by: Thomas Roberts <5656702+opr@users.noreply.github.com> * Remove debug * Revise type (remove as) * rename to unregisteredSubContexts * getNoticeContexts comment * Add test for unregistered errors * Update comment Co-authored-by: Thomas Roberts <5656702+opr@users.noreply.github.com> |
||
---|---|---|
.. | ||
active-filters | ||
attribute-filter | ||
cart | ||
cart-checkout-shared | ||
catalog-sorting | ||
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-results-count | ||
product-search | ||
product-tag | ||
product-top-rated | ||
products | ||
products-by-attribute | ||
rating-filter | ||
reviews | ||
shared/styles | ||
single-product | ||
stock-filter | ||
store-notices | ||
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.