This repository has been archived by the owner on Feb 13, 2023. It is now read-only.
🚑️ Inherit content-type
from options first
#51
Merged
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.
Fix the regression of
content-type
that is brought from #46.New Pull Request Checklist
main
branch to avoid conflicts (via merge from master or rebase)Additional context and info (if any)
The proper order to determine which
content-type
should be used is:Options.headers['content-type']
Options.contentType
BaseOptions.contentType
Headers.jsonContentType
And after #46, it's been changed to:
Options.headers['content-type']
Options.contentType
Headers.jsonContentType
Which dropped the content type set in the
BaseOptions
.