c3f4310fe2
* Add TotalsWrapper component and associated styling * Add TotalsWrapper around the subtotal, fees and discount * Remove margins/paddings/borders from sidebar elements This is to allow TotalsWrapper to be the component responsible for handling spacing and borders. * Update styles to allow components to be wrapped in TotalsWrapper * Move TotalsWrapper to checkout package * Wrap all parts of Cart sidebar in TotalsWrapper * Remove border from coupon panel * Add has-bottom-border option to TotalsWrapper * Wrap checkout sidebar components in TotalsWrapper * Remove border/padding from order summary * Add hasValidFills function This will be used to check if a Slot has any fills that return truthy values. * Remove borderSize and hasBottomBorder props from TotalsWrapper * Wrap Slots in TotalsWrapper * Update hasValidFills to check length of array * Update tests and snapshots * Only render tax totals if tax is more than 0 |
||
---|---|---|
.. | ||
active-filters | ||
attribute-filter | ||
cart-checkout | ||
featured-category | ||
featured-product | ||
handpicked-products | ||
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 | ||
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.