9bb7cd7b8b
* Apply Rector suggestions * Add changefile(s) from automation for the following project(s): woocommerce * Restore false positive $missing_tables will always be an array * Restore false positive. Rector issue: AddDefaultValueForUndefinedVariableRector. This time the early return is valid so there’s no need to move the $process_limit assignment to the top. * Ask if $orders is an array $orders is used as an array lines below. Add `is_array` just in case the “paginate” param is used which would change $orders to an object. * Check if variable is array Simplifies variable check given that they are used as an array lines below. * Restore code as taxes is always an array * Restore false positive In the previous loop the $data variable is being built as an array of arrays. Then $value in this loop will allways be array. * Restore false positive get_children’s method. of a WC_Product instance will always return an array. * Simplify variable check Ask if varialbe is array since it only can be array or false. * Restore false positive WC_Blocks_Utils::get_blocks_from_page() will always return an array. * Restore false positive There’s a check asking if $existing_meta_data[ $meta_data->key ] is array. * Restore false positive $child_ids will always be an array. * Restore false positives WC_Product->get_visible_children() will always return an array. * Restore false positives WC_Product->get_children() will always return an array. * Restore false positive WC_Product->get_visible_children() will always return an array. * Restore false positive WC_Order->get_items() will always return an array. * Restore false positive The get_matching_rates private method will always return an array. Updated the @return declaration to be an array instead of boolean. * Remove unnecessary array type casting. * Restore false positive $this->get_children() will always return an array. * Fix lint issues * Remove unnecessary default assignment * Remove unnecessary is_array check * Remove unnecessary is_array check * Remove unnecessary is_array check * Change default value from null to false * Remove unnecessary is_array check * Update changelog entry * Update changelog entry * Update changelog entry * Add changefile(s) from automation for the following project(s): woocommerce * Update changelog entry * Use self for consistency --------- Co-authored-by: github-actions <github-actions@github.com> |
||
|---|---|---|
| .github | ||
| .husky | ||
| bin | ||
| changelog | ||
| docs | ||
| packages | ||
| plugins | ||
| tools | ||
| .codecov.yml | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .gitattributes | ||
| .gitignore | ||
| .markdownlint.json | ||
| .markdownlintignore | ||
| .npmrc | ||
| .nvmrc | ||
| .pnpmfile.cjs | ||
| .prettierrc.js | ||
| .stylelintrc | ||
| .syncpackrc | ||
| CODEOWNERS | ||
| CODE_OF_CONDUCT.md | ||
| DEVELOPMENT.md | ||
| README.md | ||
| SECURITY.md | ||
| changelog.txt | ||
| package.json | ||
| phpcs.xml | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| renovate.json | ||
| tsconfig.base.json | ||
README.md
WooCommerce Monorepo
Welcome to the WooCommerce Monorepo on GitHub. Here you can find all of the plugins, packages, and tools used in the development of the core WooCommerce plugin as well as WooCommerce extensions. You can browse the source, look at open issues, contribute code, and keep tracking of ongoing 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.
Getting Started
To get up and running within the WooCommerce Monorepo, you will need to make sure that you have installed all of the prerequisites.
Prerequisites
- NVM: While you can always install Node through other means, we recommend using NVM to ensure you're aligned with the version used by our development teams. Our repository contains an
.nvmrcfile which helps ensure you are using the correct version of Node. - PNPM: Our repository utilizes PNPM to manage project dependencies and run various scripts involved in building and testing projects.
- PHP 7.4+: WooCommerce Core currently features a minimum PHP version of 7.4. It is also needed to run Composer and various project build scripts. See troubleshooting for troubleshooting problems installing PHP.
- Composer: We use Composer to manage all of the dependencies for PHP packages and plugins.
Once you've installed all of the prerequisites, you can run the following commands to get everything working.
# Ensure that you're using the correct version of Node
nvm use
# Install the PHP and Composer dependencies for all of the plugins, packages, and tools
pnpm install
# Build all of the plugins, packages, and tools in the monorepo
pnpm build
At this point you are now ready to begin developing and testing. All of the build outputs are cached running pnpm build again will only build the plugins, packages, and tools that have changed since the last time you ran the command.
Check out our development guide if you would like a more comprehensive look at working in our repository.
Repository Structure
- Plugins: Our repository contains plugins that relate to or otherwise aid in the development of WooCommerce.
- WooCommerce Core: The core WooCommerce plugin is available in the plugins directory.
- Packages: Contained within the packages directory are all of the PHP and JavaScript provided for the community. Some of these are internal dependencies and are marked with an
internal-prefix. - Tools: We also have a growing number of tools within our repository. Many of these are intended to be utilities and scripts for use in the monorepo, but, this directory may also contain external tools.
Reporting Security Issues
To disclose a security issue to our team, please submit a report via HackerOne here.
Support
This repository is not suitable for support. Please don't use our issue tracker for support requests, but for core WooCommerce issues only. Support can take place through the appropriate channels:
- If you have a problem, you may want to start with the self help guide.
- The Woo.com premium support portal for customers who have purchased themes or extensions.
- Our community forum on wp.org which is available for all WooCommerce users.
- The Official WooCommerce Facebook Group.
- For customizations, you may want to check our list of WooExperts or Codeable.
NOTE: Unfortunately, we are unable to honor support requests in issues on this repository; as a result, any requests submitted in this manner will be closed.
Community
For peer to peer support, real-time announcements, and office hours, please join our slack community!
Contributing to WooCommerce
If you have a patch or have stumbled upon an issue with WooCommerce core, you can contribute this back to the code. Please read our contributor guidelines for more information on how you can do this.