feat(workflows): Data aggregation

[adrien2p]

What

• Add new pipe options to merge the data and have the ability to configure how to merge the data
  • merge - mergeAlias - mergeFrom
• Also fix integration tests and apply the non retrieval in the cart workflow, meaning updating the end point as well

[changeset-bot]

⚠️ No Changeset found

Latest commit: 064aac7

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

[vercel]

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

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
medusa-docs	⬜️ Ignored (Inspect)	Visit Preview		Aug 10, 2023 10:22am

[olivermrbl]

LGTM, @carlos-r-l-rodrigues to sign off too 💪

[carlos-r-l-rodrigues]

Nice

[olivermrbl]

question: Why do we only want to merge before the last handler? My steps broke after merging in these changes, because my middlewares were expecting the merged data shape too.

[adrien2p]

The idea was to merge everything including the middleware result as we discussed on slack no? Previously, when used manually you could have placed the aggregator at any position you wanted before or after middleware's are applied, you can decide tou not use the automatic merge and instead use it manually, it is also possible.

Do you mean that instead we could apply it before every handlers?