## What Replace AddressFields with actual AddressPayload schema based off the actual type used by the controllers. ## Why AddressPayload is currently being referenced in client code. Our OAS schema should attempt to match current client usage in order to reduce friction when migrating to a OAS generated types package. ## How * Represent AddressPayload and AddressCreatePayload in our OAS schemas. * Replace reference to AddressFields * Plus, fix typo in /admin/orders/ route
6 lines
91 B
Markdown
6 lines
91 B
Markdown
---
|
|
"@medusajs/medusa": patch
|
|
---
|
|
|
|
feat(oas): add @schema OAS for address request payloads
|