-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
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
feat!: Do not treat Buffers as JSON by default #621
Conversation
…o upgrade-node-fetch
Warning: This pull request is touching the following templated files:
|
…o do-not-treat-buffer-as-json
…o do-not-treat-buffer-as-json
…o do-not-treat-buffer-as-json
…o do-not-treat-buffer-as-json
`node-fetch` does not yet support webstreams, which is required for `.body` node-fetch/node-fetch#387
Is there a FR tied to this? |
@sofisl more-so bug reports and difficult to catch behavior: |
@@ -1112,22 +1112,6 @@ describe('🍂 defaults & instances', () => { | |||
assert.deepStrictEqual(res.data, {}); | |||
}); | |||
|
|||
it('should set content-type to application/json by default, for buffer', async () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we write a test that asserts the behavior for what happens if a buffer does get sent in?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, it’s mostly a partial revert of:
but that can be added.
Dependency:
node-fetch
v3 #617🦕