4b30e78ae6
* Filters: Remove filterPaths, add path as property to filters object * Set a default path, so we only need to configure it for changed paths * Fix nav & filter fetching for nested lists * Add “go back” functionality to all subfilter lists, not only ones with components set * Make label optional on component options * Update documentation to remove mention of filterpaths * Add documentation on the filters structure |
||
|---|---|---|
| .. | ||
| animation-slider | ||
| calendar | ||
| card | ||
| chart | ||
| count | ||
| dropdown-button | ||
| ellipsis-menu | ||
| filters | ||
| flag | ||
| gravatar | ||
| higher-order/use-filters | ||
| link | ||
| order-status | ||
| pagination | ||
| product-image | ||
| rating | ||
| segmented-selection | ||
| split-button | ||
| summary | ||
| table | ||
| README.md | ||
| index.js | ||
README.md
Components
This folder contains the WooCommerce-created components. These are exported onto a global, wc.components, for general use.
How to use:
For any files not imported into components/index.js (analytics/*, layout/*, dashboard/*, etc), we can use import { Card, etc … } from @woocommerce/components.
For any component/* files, we should import from component-specific paths, not from component/index.js, to prevent circular dependencies. See components/card/index.js for an example.
import { Card, Link } from '@woocommerce/components';
render: function() {
return (
<Card title="Card demo">
Card content with an <Link href="/">example link.</Link>
</Card>
);
}
For external development
External developers will need to enqueue the components library, wc-components, and then can access them from the global.
const { Card, Link } = wc.components;
render: function() {
return (
<Card title="Card demo">
Card content with an <Link href="/">example link.</Link>
</Card>
);
}