96925f77fa
* Move component lifecycle method to top of component * Update rows if the rows passed in via props have changed This lets us bring in API changes, but will wipe out any sorting (revisit in a later PR, perhaps) * Pass rows through to Table even if we don’t have rows loaded yet Adds todo comment to remind that we should come back to add a placeholder/loading state |
||
|---|---|---|
| .. | ||
| bin | ||
| client | ||
| languages | ||
| lib | ||
| tests | ||
| .babelrc | ||
| .distignore | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc | ||
| .gitignore | ||
| .travis.yml | ||
| Gruntfile.js | ||
| README.md | ||
| package-lock.json | ||
| package.json | ||
| phpcs.xml.dist | ||
| phpunit.xml.dist | ||
| wc-admin.php | ||
| webpack.config.js | ||
README.md
WooCommerce Admin
This is a feature plugin for a modern, javascript-driven WooCommerce Admin experience.
Prerequisites
Gutenberg and WooCommerce should be installed prior to activating the WooCommerce Admin feature plugin. You also need v3 of the WooCommerce REST API via wc-api-dev or the feature branch.
For better debugging, it's also recommended you add define( 'SCRIPT_DEBUG', true ); to your wp-config. This will load the unminified version of all libraries, and specifically the development build of React.
Development
After cloning the repo, install dependencies with npm install. Now you can build the files using one of these commands:
npm run build: Build a production versionnpm start: Build a development version, watch files for changes
There are also some helper scripts:
npm run lint: Run eslint over the javascript filesnpm run i18n: Create a PHP file with the strings from the javascript files, used to get around lack of JS support in WordPress.org.