5a1bbbefb9
* Update NPM packages * Switch JSON dependencies to new PHP files * include->require * include->require * Remove from package and run audit fix * Update wp-prettier * Use version from asset file * Fix eslint issues and test failures * Update OriginalComponent docblocks * Props are objects, not arrays * Array to Object * fix tests throwing unhandled rejection errors in node. These tests were all testing Promise.rejects but then not properly catching the reject in the assertions. * exclude rule for no short array syntax allowed This is a WordPress core standard that we choose to ignore because it’s silly in our context to follow that rule (and we’re being consistent with WooCommerce Admin). |
||
|---|---|---|
| .. | ||
| collections | ||
| query-state | ||
| schema | ||
| utils | ||
| README.md | ||
| constants.js | ||
| index.js | ||
README.md
This folder contains all the data stores registered with wp.data for use by various blocks. Store keys are exported as constants on the wc.wcBlocksData export (external registered as @woocommerce/block-data and enqueued via handle wc-blocks-data-store). For any block using the store, make sure you import the store key rather than using the reference directly to ensure dependencies are automatically extracted correctly.
It is assumed there is some familiarity already with interacting with the wp.data api. You can read more about that here.
The following stores are registered:
| store | description | store key |
|---|---|---|
| schema | Used for accessing routes. Has more internal usage. | SCHEMA_STORE_KEY |
| collections | Holds collections of data indexed by namespace, model name and query string | COLLECTIONS_STORE_KEY |
| query-state | Holds arbitrary values indexed by context and key. Typically used for tracking state of query objects for a given context | QUERY_STATE_STORE_KEY |