36c1bb7361
* Provider progress * Revert nonce change for debugging * Working emitters * Fix dismiss link alignment in notices * Fix button state and double adds * Remove old context file * Add type defs * Fix context name * Leftovers from merge * Hooks up the variation picker to cart context * Group event emitters in context * Fix external product display * Pass product through to VariationAttributes * Pass around dispatchers * Update assets/js/base/context/add-to-cart-form/form-state/reducer.js Co-authored-by: Darren Ethier <darren@roughsmootheng.in> * Update assets/js/atomic/blocks/product-elements/add-to-cart/product-types/variable/variation-attributes/attribute-select-control.js Co-authored-by: Darren Ethier <darren@roughsmootheng.in> * Update assets/js/base/context/add-to-cart-form/form-state/reducer.js Co-authored-by: Darren Ethier <darren@roughsmootheng.in> * remove placeholder comment * content->container * Clarify variation method comment * update comment * Switch nesting of providers * Variation attribute utils test coverage * If nothing is selected yet, just return all variations. * Comments to explain loops * Use refs to avoid recalculation of attributes on every render * Update memo usage * typo * move mock data to test file * Switch to useShallowEqual * trigger cart fragment refresh after add to cart * Decode option entities Co-authored-by: Darren Ethier <darren@roughsmootheng.in> |
||
|---|---|---|
| .. | ||
| 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.
Saving
Usually blocks can be converted to HTML in the save function, so that what's saved into the database is the same HTML that's rendered on the frontend. Our blocks are different since they need to show the latest products and reflect any changes to products.
The grid blocks are saved as shortcodes using getShortcode, but the Featured Product block is considered a "dynamic block", so we use PHP to build that each time the post is loaded on the frontend. The code for that is set up when the block is registered in PHP, and lives in WGPB_Block_Featured_Product.