6802b2720a
* Add MarketingRecommendations feature. The code here is based on other feature with default fallbacks and with data source poller, e.g. see payment gateway suggestions. * Use MarketingRecommendations feature in API. * Add spec_key for MarketingRecommendationsDataSourcePoller. If we don't specify it, the default is `id`, which is not used in our recommendation data, and this will cause things not to work as expected. * Recursively convert object to array. This is because all the subsequent functions work with arrays, not objects. * Make recommended marketing tools and coupons use MarketingRecommendationsInit. This is so that recommended channels, tools, and coupons make use of the same transient data with data source poller. * Add changelog. * Fix PHP lint issues. * Add doc comment to fix lint error. * Fix tests in MarketingRecommendationsTest. * Replace recommendations.json file with generated data in DefaultMarketingRecommendations. This is to have i18n support. * Add icons for fallback marketing recommendations. * Fix PHP linting issue. * Fix linting issue. * Fix failing tests with PHP 8.0. * Remove unused replaced code in MarketingSpecs. * Remove unneeded false check. This is because `is_array` would return `false` when `false` is being passed as the argument. Co-authored-by: Bartosz Budzanowski <bartosz.budzanowski@automattic.com> --------- Co-authored-by: Bartosz Budzanowski <bartosz.budzanowski@automattic.com> |
||
---|---|---|
.. | ||
.wordpress-org | ||
assets | ||
bin | ||
changelog | ||
client | ||
i18n | ||
includes | ||
lib | ||
packages | ||
patterns | ||
sample-data | ||
src | ||
templates | ||
tests | ||
.distignore | ||
.eslintignore | ||
.eslintrc.js | ||
.gitattributes | ||
.gitignore | ||
.wp-env.json | ||
NEXT_CHANGELOG.md | ||
README.md | ||
composer.json | ||
composer.lock | ||
license.txt | ||
package.json | ||
phpcs.xml | ||
phpunit.xml | ||
readme.txt | ||
tsconfig.json | ||
uninstall.php | ||
woocommerce.php |
README.md
This is the WooCommerce Core plugin. Here you can browse the source and keep track of development. We recommend all developers to follow the WooCommerce development blog to stay up to date about everything happening in the project. You can also follow @DevelopWC on Twitter for the latest development updates.
If you are not a developer, please use the WooCommerce plugin page on WordPress.org.
Getting Started
Please make sure you follow the repository's getting started guide first!
# Make sure that WooCommerce Core and all of its dependencies are built
pnpm --filter=@woocommerce/plugin-woocommerce build
# Make sure you're in the WooCommerce Core directory
cd plugins/woocommerce
# Start the development environment
pnpm -- wp-env start
You should now be able to visit http://localhost:8888/
and access WooCommerce environment.
Building Components
There are two major client-side components included in WooCommerce Core that can be built, linted, and tested independently. We've organized these components in this way to take advantage of caching to prevent unnecessarily performing expensive rebuilds when only working in one of them.
plugins/woocommerce/client/legacy
This directory contains the Classic CSS and jQuery code for WooCommerce.
# Build the assets.
pnpm --filter=@woocommerce/classic-assets build
# Lint the assets.
pnpm --filter=@woocommerce/classic-assets lint
plugins/woocommerce-admin
This directory contains the React-based admin interface.
# Build the React-based admin client.
pnpm --filter=@woocommerce/admin-library build
# Lint the React-based admin client.
pnpm --filter=@woocommerce/admin-library lint
# Test the React-based admin client.
pnpm --filter=@woocommerce/admin-library test
plugins/woocommerce-blocks
This directory contains the client for WooCommerce + Gutenberg.
# Build the Blocks client.
pnpm run --filter=@woocommerce/block-library build
# Lint the Blocks client.
pnpm run --filter=@woocommerce/block-library lint
# Test the Blocks client.
pnpm run --filter=@woocommerce/block-library test
Helper Scripts
Here is a collection of scripts that can help when developing the React-based admin interface.
# Create a develoment build of the React-based admin client.
pnpm --filter=@woocommerce/admin-library dev
# Create and watch a development build of the React-based admin client.
pnpm --filter=@woocommerce/admin-library start
# Watch the tests of the React-based admin client.
pnpm --filter=@woocommerce/admin-library test:watch
# Run a type check over the React-based admin client's TypeScript files.
pnpm --filter=@woocommerce/admin-library ts:check
Documentation
- WooCommerce Documentation
- WooCommerce Developer Documentation
- WooCommerce Code Reference
- WooCommerce REST API Docs
Reporting Security Issues
To disclose a security issue to our team, please submit a report via HackerOne here.