73d1432b02
* Hook up checkout validation with context * Make sure hasValidationErrors is up to date in onCheckoutProcessing * Move validation check inside CheckoutProcessor's processCheckout * Make sure all checkout form fields have a unique ID * Don't clear checkout context errors in shipping context * Move CheckoutProcessor to the top so scrollToTop works * Do not disable Place Order Button if there are errors * Split checkValidation and processCheckout in Checkout Provider * Refactor event emitter to use Maps * Save payment method errors to validation context * Show an notice when a payment method has an error * Make sure JS errors during payment are displayed * Remove error notice when payment method doesn't return an error anymore * Make sure payment methods know if shipping and billing addresses are the same * Make sure checkout is only processed if payment methods didn't fail * Make sure state input also has an id * Clear input and select errors on unmount * Pass id to CountryInput and StateInput * Fix function name * Add missing default context values * Move onCheckoutCompleteError effect to CheckoutBlock * Remove conditional from shipping setHasError |
||
|---|---|---|
| .. | ||
| 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 | ||
| 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.