medusa-store

9,018 Commits 2 Branches 0 Tags

2 Commits

Author	SHA1	Message	Date
Leonardo BeniniandGitHub	458dd04bbf	fix(core-flows,types,medusa): pass /store/shipping-options fields to workflow (#13527 ) cc @willbouch since you asked to be tagged if I opened this PR. The /store/shipping-options is one of only 2 store endpoints to not allow custom `fields` to be passed(other one is /store/returns if you guys want to add it to the backlog). This PR fixes that so that custom linked models can also be retrieved. Note: This fix reveals a bug in the next.js starter https://github.com/medusajs/nextjs-starter-medusa/blob/eac359cc8d52f1d33d8712e18e4e0f38940afb3e/src/lib/data/fulfillment.ts#L23-L24 `fields` was previously ignored, now it errors since it tries to parse the misspelled "fulfllment"(the i is missing). It worked before since both fields are already defined by default inside the workflow. So the `fields` line is totally redundant and should be removed(ideally before merging this). Maybe in the next release notes it should also warn users to remove it for those that already have a modified copy of the starter.	2025-09-22 13:31:59 +00:00
Leonardo Benini GitHub William Bouchard	1b30b656b3	fix(js-sdk): skip null values in query qs.stringify (#13460 ) * escape null values in qs.stringify * skip null values --------- Co-authored-by: William Bouchard <46496014+willbouch@users.noreply.github.com>	2025-09-12 12:07:56 -04:00

Author

SHA1

Message

Date

Leonardo BeniniandGitHub

458dd04bbf

fix(core-flows,types,medusa): pass /store/shipping-options fields to workflow (#13527 )

cc @willbouch since you asked to be tagged if I opened this PR.

The /store/shipping-options is one of only 2 store endpoints to not allow custom `fields` to be passed(other one is /store/returns if you guys want to add it to the backlog). This PR fixes that so that custom linked models can also be retrieved.

Note: This fix reveals a bug in the next.js starter

https://github.com/medusajs/nextjs-starter-medusa/blob/eac359cc8d52f1d33d8712e18e4e0f38940afb3e/src/lib/data/fulfillment.ts#L23-L24

`fields` was previously ignored, now it errors since it tries to parse the misspelled "fulfllment"(the i is missing). It worked before since both fields are already defined by default inside the workflow. So the `fields` line is totally redundant and should be removed(ideally before merging this).   
Maybe in the next release notes it should also warn users to remove it for those that already have a modified copy of the starter.

2025-09-22 13:31:59 +00:00

1b30b656b3

fix(js-sdk): skip null values in query qs.stringify (#13460 )

* escape null values in qs.stringify

* skip null values

---------

Co-authored-by: William Bouchard <46496014+willbouch@users.noreply.github.com>

2025-09-12 12:07:56 -04:00