-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature: introduce additional_data to the product endpoints #8405
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
5 Skipped Deployments
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔥
Co-authored-by: Oli Juhl <[email protected]>
…8436) * feat(core-flows,payment,medusa,types): add ability to set and manage refund reasons * fix(payment): validate total amount when refunding payment (#8437) Co-authored-by: Carlos R. L. Rodrigues <[email protected]> * feature: introduce additional_data to the product endpoints (#8405) * chore(docs): Generated References (#8440) Generated the following references: - `product` * chore: align payment database schema * Update packages/core/core-flows/src/payment-collection/steps/create-refund-reasons.ts Co-authored-by: Oli Juhl <[email protected]> * chore: address review --------- Co-authored-by: Carlos R. L. Rodrigues <[email protected]> Co-authored-by: Harminder Virk <[email protected]> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Oli Juhl <[email protected]>
Fixes: FRMW-2647, FRMW-2648
First approach of introducing and consuming additional data.
AdminCreateProduct
to now includeadditional_data
as part of the payload.additional_data
as an arbitrary object. But then also, use merge the user-defined validator (if exists). This change might impact some other parts of the codebase.additional_data
and rest of the properties and pass them to the workflow as needed.