We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
mergeBasket
Content-Type: application/json
ShopperBaskets.mergeBasket requires the content-type application/json or it fails with an HTTP 415 (unsupported media type).
ShopperBaskets.mergeBasket
application/json
The API itself is a bit odd, in that no request body is needed, so this behaviour is sorta unexpected.
Maybe our existing logic is looking for the existence of a required request payload to send this header:
commerce-sdk-isomorphic/templates/operations.ts.hbs
Lines 170 to 172 in 0d2cdea
It might be a safe default to always send it or alternatively special case this method.
Alternatively, maybe we could request a change to the RAML. 🤷
The workaround for customers is to provide the header manually:
const mergeResponse = await new capi.ShopperBaskets( clientConfig ).mergeBasket({ headers: { "Content-Type": "application/json", }, parameters: { createDestinationBasket: true }, })
Here is a sample script showing the behaviour:
https://gist.github.com/johnboxall/eed791f95ad6636baa01269a1d178bbb
The text was updated successfully, but these errors were encountered:
This issue has been linked to a new work item: W-12659232
Sorry, something went wrong.
Hi @johnboxall, thanks for bringing this to our attention. This work has been added to our backlog and we'll loop you back in when we have updates.
No branches or pull requests
ShopperBaskets.mergeBasket
requires the content-typeapplication/json
or it fails with an HTTP 415 (unsupported media type).The API itself is a bit odd, in that no request body is needed, so this behaviour is sorta unexpected.
Maybe our existing logic is looking for the existence of a required request payload to send this header:
commerce-sdk-isomorphic/templates/operations.ts.hbs
Lines 170 to 172 in 0d2cdea
It might be a safe default to always send it or alternatively special case this method.
Alternatively, maybe we could request a change to the RAML. 🤷
The workaround for customers is to provide the header manually:
Here is a sample script showing the behaviour:
https://gist.github.com/johnboxall/eed791f95ad6636baa01269a1d178bbb
The text was updated successfully, but these errors were encountered: