* Add unique ID attribute to Product Collection block
In this update, we introduced a unique identifier for each instance of the Product Collection block. This change involves several key modifications:
1. **Block JSON Update**: Added a new `id` attribute in `block.json` to store the unique identifier for each block instance.
2. **Product Collection Content Update**: In `product-collection-content.tsx`, we utilized the `uuid` library to generate a unique ID. This is done in a `useEffect` hook, ensuring that each block instance receives a distinct ID upon initialization.
3. **Type Definitions**: The `ProductCollectionAttributes` interface in `types.ts` was updated to include the new `id` attribute, aligning with our enhanced data structure.
4. **Package Dependencies**: To support this feature, `@types/uuid` and `uuid` were added to `package.json`, ensuring we have the necessary tools for ID generation.
This enhancement is pivotal for uniquely identifying each Product Collection block, paving the way for more robust and individualized block handling in the future.
* Rename uniqueId to id
* Add lock file
* Add 'id' context to product collection and template
* Add changefile(s) from automation for the following project(s): woocommerce-blocks
* Merge trunk with 42861-introduce-a-unique-identifier-for-each-product-collection-block
* Regenerate the lockfile
* Remove autogenerated change in plugins/woocommerce/package.json
* Regenerate lock file
* Rerun CI actions
* Delete pnpm-lock.yaml file & regenerate it using pnpm install command
---------
Co-authored-by: github-actions <github-actions@github.com>
This bumps the version to 0.14.3 so that we can take advantage of some
upstream improvements. It also makes some changes to the way our
builds and watches work to minimize the number of unnecessary
Node processes involved in the execution.
This adds support for using the `pnpm utils ci-jobs` command in our `ci.yml` file. One of the bigger benefits to this change too is that we're now distributing a bundled version of the utils tool. This lets us run it without actually having to install the repo and will let us speed up any workflows that currently do.
* Add @wordpress/core-data dependency
* Update lock file
* Implement useLayoutTemplate
* Changelog
* Allow layoutTemplateId param to be undefined
* Only enable useEntityRecord when layoutTemplateId is set
* Workaround for query made when layoutTemplateID is not set
* Use getEntityConfig instead of getEntity
* Update comment with core-data version
* Add doc for useLayoutTemplate
* Add expression-evaluation package
* Export useEvaluationContext
* Add HOC to hide collapsible block when nothing is inside it
* Add changelog
* Create a separate place for WP hooks and move existing hook to it
* Reintroduce line deleted automatically
* Refactor to useSelect
* Clean up created pages and posts
* Move tax tests so that they run last
* Improve locators
* Changelog
* Improve locators
* Improve locator on heading
* Change assertions to look for alert text
* Change assertion to look for text
* Update locators
* Update locator
* Update alternate elements
* Specify first order amount
* Update locator
* Changelog
* Increase reliability of checkout test
* Update a few locators
* Remove .slice()
* Add some console output to checkout test
* Make command palette tests Mac-compatible
* Added update for why download test flaky
* Improvements to checkout tax tests
* Add changelog
* Assert on range of prices
* Improve the regex for matching the price
* Changelog
* Clean up locator
* Unskip analytics tests
* Remove logging statements
* Update variations selector
* Remove comment
* Fix disable block tests
* Remove skipped legacy coupon page test
* Account for multiple products in test
* Cleaned up some console.logs
* Added specificity to locator
* Better price parsing
* Fix cart block shipping test
* Fix syntax error
* Update Playwright, fix logic error
---------
Co-authored-by: Jon Lane <jon.lane@automattic.com>
Wireit doesn't allow us to have build outputs in a directory outside
of the package. We can get around this by having a build step in
WooCommerce that copies the files from the output directories.
We're adding this to _every_ package since they have their own
configuration and scripts to run. This also keeps them
isolated so that they can operate independently.