861bc091d4
* Initial implementation of the missing product state - Changed `getProductCollectionUIStateInEditor` to a hook `useProductCollectionUIState`. - As we added logic to check if selected product reference is deleted which require making an API call. Therefore, I decided to use a hook. - While making an API call to check if product reference is deleted, I decided to show spinner in the block. - Introduced new UI state `DELETED_PRODUCT_REFERENCE` to handle the missing product state. - Updated existing `ProductPicker` component to handle the new UI state. - It's better to use existing component for the missing product state, as it already has all the required UI. * Add changefile(s) from automation for the following project(s): woocommerce-blocks * Use getEntityRecord to check if product exists and other improvements * Remove console log * Add E2E tests for deleted product reference in Product Collection block This commit introduces new E2E tests to verify the behavior of the Product Collection block when dealing with deleted product references. The changes include: 1. New test suite in register-product-collection-tester.block_theme.spec.ts 2. Modification to product-collection.page.ts to support custom product selection 3. Minor update to utils.tsx to handle trashed products These tests ensure that the Product Collection block correctly handles scenarios where referenced products are deleted, trashed, or restored, improving the overall reliability of the feature. * Simplify product creation in Product Collection block test * Refactor E2E test for delete product reference picker 1. Removing the unnecessary `test.describe` block for "Deleted product reference" 2. Eliminating the `beforeEach` hook that was creating a test product 3. Integrating the test product creation directly into the main test This change simplifies the test structure and improves readability while maintaining the same test coverage for the Product Collection block's behavior when dealing with deleted or unavailable products. * Simplify logic for product collection UI state This commit simplifies the handling of the `usesReference` prop in the Product Collection block: 1. In `edit/index.tsx`, directly pass `usesReference` to `useProductCollectionUIState` hook without conditional spreading. 2. In `utils.tsx`, update the type definition of `usesReference` in the `useProductCollectionUIState` hook to explicitly include `undefined`. * Refactor Product Collection block to improve prop passing - Introduce ProductCollectionContentProps type for better prop management - Refactor Edit component to use a renderComponent function - Update component prop types to use more specific props - Remove unnecessary props from ProductCollectionEditComponentProps - Simplify component rendering logic in Edit component - Adjust ProductPicker to receive only required props - Update imports and prop types in various files to use new types This refactoring improves code organization and reduces prop drilling by only passing necessary props to each component. It enhances maintainability and readability of the Product Collection block and related components. * Refactor Product Collection block editor UI state handling This commit simplifies the rendering logic in the Product Collection block's Edit component. It removes a redundant case for the VALID state, as both VALID and VALID_WITH_PREVIEW states now render the same ProductCollectionContent component. This change improves code maintainability and reduces duplication. * Fix: isDeletedProductReference is not set correctly * Use "page.reload" instead of "admin.page.reload" * Separate PRODUCT_REFERENCE_PICKER and DELETED_PRODUCT_REFERENCE cases This improves readability and maintainability of the switch statement. --------- Co-authored-by: github-actions <github-actions@github.com> |
||
|---|---|---|
| .. | ||
| .wordpress-org | ||
| assets | ||
| bin | ||
| changelog | ||
| client | ||
| i18n | ||
| includes | ||
| lib | ||
| packages | ||
| patterns | ||
| sample-data | ||
| src | ||
| templates | ||
| tests | ||
| .distignore | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .gitattributes | ||
| .gitignore | ||
| .phpunit-watcher.yml | ||
| .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 development 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.