fix(interceptors): prevent overriding existing headers #34
Conversation
This file contains hidden or 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
Convly
added
the
source: client-interceptors
jhoward1994
reviewed
Jan 30, 2025
jhoward1994
approved these changes
Jan 30, 2025
Contributor
|
Tested, works for me! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What does it do?
Make sure the
setDefaultHeadersHTTP interceptor doesn't override manually set headers.Why is it needed?
see #27
How to test it?
Using
sdk.fetchwith a custom content type header should not override said header withapplication/jsonAlternatively, running the unit tests ensures the behavior is correct based on
tests/unit/sdk.test.tsandtests/unit/sdk.test.tsRelated issue(s)/PR(s)
fix #27