39b6c1c320
* Fix notice persistence after dismissal - This fix applied to the `incompatible payment gateway notice`. - We used the same dismissal logic in the `sidebar compatibility notice` * Get incompatible payments when initialized We initially get the list of `globalPaymentMethods` shared from the back-end as incompatible payments, because the front-end `availablePaymentMethods` is empty before the `paymentMethodsInitialized` state * Introduce advanced notice dismissal handling We want to display a dismissed incompatible gateways notice, when the list of incompatible gateways is updated (e.g., a new incompatible gateway is enabled) * Use the full block name for the `Cart` & `Checkout` * Update variable name for comprehension * Fix TS errors * Remove unused imports |
||
|---|---|---|
| .. | ||
| components | ||
| context | ||
| hocs | ||
| hooks | ||
| utils | ||
| README.MD | ||
README.MD
Base Components/Context/Hooks
Base components are designed to be used on the frontend of a store. Due to this, we need to avoid using heavy WordPress externals as dependencies (wp-components, wp-block-editor, etc). To get around this, import from a local package instead.
e.g. Instead of importing from @wordpress/components, use:
import { Component } from 'wordpress-components';
Check the built *.assets.php files to ensure extra dependencies aren't being added to the build.