feat: add hooks to product module's workflows

[thetutlage]

Fixes: FRMW-2641

In this PR we have introduce hooks within the product module's workflows. Following is the collection of workflows and hooks they expose.

Create action workflows

createCollectionsWorkflow

• Hook: collectionsCreated
• Input: { collections: ProductCollectionDTO[], additional_data?: AdditionalData }

createProductOptionsWorkflow

• Hook: productOptionsCreated
• Input: { product_options: ProductOptionDTO[], additional_data?: AdditionalData }

createProductTagsWorkflow

• Hook: productTagsCreated
• Input: { product_tags: ProductTagDTO[], additional_data?: AdditionalData }

createProductTypesWorkflow

• Hook: productTypesCreated
• Input: { product_types: ProductTypeDTO[], additional_data?: AdditionalData }

createProductVariantsWorkflow

• Hook: productVariantsCreated
• Input: { product_variants: ProductVariantDTO[], additional_data?: AdditionalData }

createProductsWorkflow

• Hook: productsCreated
• Input: { products: ProductDTO[], additional_data?: AdditionalData }

Update action workflows

updateCollectionsWorkflow

• Hook: collectionsUpdated
• Input: { collections: ProductCollectionDTO[], additional_data?: AdditionalData }

updateProductOptionsWorkflow

• Hook: productOptionsUpdated
• Input: { product_options: ProductOptionDTO[], additional_data?: AdditionalData }

updateProductTagsWorkflow

• Hook: productTagsUpdated
• Input: { product_tags: ProductTagDTO[], additional_data?: AdditionalData }

updateProductTypesWorkflow

• Hook: productTypesUpdated
• Input: { product_types: ProductTypeDTO[], additional_data?: AdditionalData }

updateProductVariantsWorkflow

• Hook: productVariantsUpdated
• Input: { product_variants: ProductVariantDTO[], additional_data?: AdditionalData }

updateProductsWorkflow

• Hook: productsUpdated
• Input: { products: ProductDTO[], additional_data?: AdditionalData }

Delete action workflows

deleteCollectionsWorkflow

• Hook: collectionsDeleted
• Input: { ids: string[] }

deleteProductOptionsWorkflow

• Hook: productOptionsDeleted
• Input: { ids: string[] }

deleteProductTagsWorkflow

• Hook: productTagsDeleted
• Input: { ids: string[] }

deleteProductTypesWorkflow

• Hook: productTypesDeleted
• Input: { ids: string[] }

deleteProductVariantsWorkflow

• Hook: productVariantsDeleted
• Input: { ids: string[] }

deleteProductsWorkflow

• Hook: productsDeleted
• Input: { ids: string[] }

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
medusa-dashboard	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 1, 2024 4:20pm

6 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
api-reference	⬜️ Ignored (Inspect)			Aug 1, 2024 4:20pm
api-reference-v2	⬜️ Ignored (Inspect)	Visit Preview		Aug 1, 2024 4:20pm
docs-ui	⬜️ Ignored (Inspect)	Visit Preview		Aug 1, 2024 4:20pm
docs-v2	⬜️ Ignored (Inspect)	Visit Preview		Aug 1, 2024 4:20pm
medusa-docs	⬜️ Ignored (Inspect)	Visit Preview		Aug 1, 2024 4:20pm
resources-docs	⬜️ Ignored (Inspect)	Visit Preview		Aug 1, 2024 4:20pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: 58c0859

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[thetutlage]

Heads up @olivermrbl @adrien2p. This is approach I am planning to take.

[olivermrbl]

LGTM, however, I would argue we should start with Products specifically. Collections, types, tags, categories are less important compared to the two former.

But perhaps, this was more for demonstration purposes?

[thetutlage]

LGTM, however, I would argue we should start with Products specifically. Collections, types, tags, categories are less important compared to the two former.

I thought by product we mean, every workflow related to products inside the core-flows/src/products/workflows directory. But anyways, I have added hooks to all these workflows.

But perhaps, this was more for demonstration purposes?
Yes, it was

_

[sradevski]

Really cool to support this, I think this should solve 80% of people's customization needs 👍

[olivermrbl]

Nice, excited about this! 🔥

[thetutlage]

There is real excitement for this 🔥

[olivermrbl]

@thetutlage, should we merge this? 🙏

[thetutlage]

Yeah. Have to update the PR description to list all hooks. I can do that post merging too