Add support for default headers in medusa-js client to support Remix/Run #1893
+54
−18
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…t headers to support Remix
|
|
@dwene is attempting to deploy a commit to the medusajs Team on Vercel. A member of the Team first needs to authorize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We're building out a storefront experience using Remix. As part of that, we needed to be able to proxy cookies from the browser to the storefront APIs (for auth, using the storefront listProducts authenticated for differing price lists, etc). I needed a way to setup the Medusa client where I could pass the Cookie header to all API requests.
This seemed like the easiest way to be able to support that.
Also, there was no storefront auth.logout in the client, so I added that here too.