0714fa41bd
* Add address-related items to wc/store/cart data store * include shippingAsBilling in return value of useCustomerData * Add useUpdateCustomerData hook This allows us to have a single hook responsible for updating the customer information on the server. * Add useUpdateCustomerData hook in Checkout block * Remove the updating customer data work from the useCustomerData hook * Remove shippingAsBilling from previousCustomerData ref type * Add useShippingAsBillingCheckbox hook * Control shippingAsBilling from single hook * Remove checkbox handling from useCheckoutAddress * Remove CustomerDataContext typedef * Merge with woocommerce/woocommerce-blocks#5810 changes * Move shipping as billing to checkout state context provider * Unused import * Subscribe to changes * Only receiveCartContents when updating customer data via checkout * Cache customerDataToUpdate * rename debounced function * Combine customerDataType and customerDataContextType * Change case of CustomerDataType * debouncedUpdateCustomerData typo * Fix notice context * Clean up inline docs for push changes * Comment on dirty state * Phone is always set * shippingAddress is never undefined * setBillingPhone * receiveCartContents explanation * Tweak customerData to avoid null * useShippingAsBilling Co-authored-by: Thomas Roberts <thomas.roberts@automattic.com> |
||
|---|---|---|
| .. | ||
| active-filters | ||
| attribute-filter | ||
| cart-checkout | ||
| checkout | ||
| featured-category | ||
| featured-product | ||
| handpicked-products | ||
| legacy-template | ||
| 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 | ||
| 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.