clientgen/{ts,js}: default content type on raw request #1717
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
|
All committers have signed the CLA. |
fredr
force-pushed
the
fredr/default-content-type
branch
from
e116385 to
86f996d
Compare
fredr
changed the title
eandre
approved these changes
Jan 17, 2025
fredr
force-pushed
the
fredr/default-content-type
branch
from
86f996d to
cfd2c55
Compare
fredr
force-pushed
the
fredr/default-content-type
branch
from
cfd2c55 to
3b099e9
Compare
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.
node-fetch will automatically figure out the content type (such as
FormData) and handle it for certain types, see https://fetch.spec.whatwg.org/#concept-bodyinit-extract and it seems like relying on that logic for raw endoints would be a sane default