Skip to content

fix: fetch response is not Readable#921

Merged
ronag merged 2 commits intomainfrom
fetch-body
Aug 3, 2021
Merged

fix: fetch response is not Readable#921
ronag merged 2 commits intomainfrom
fetch-body

Conversation

@ronag
Copy link
Copy Markdown
Member

@ronag ronag commented Aug 3, 2021

It's much easier to implement spec compliant fetch API if we don't try to be node streams at the same time.

@ronag ronag requested a review from mcollina August 3, 2021 15:20
@ronag ronag force-pushed the fetch-body branch 14 times, most recently from b5cafb5 to 5c04570 Compare August 3, 2021 15:40
Comment thread lib/api/api-fetch.js Outdated
@ronag ronag force-pushed the fetch-body branch 4 times, most recently from bb93ef2 to 93fc2b9 Compare August 3, 2021 15:51
@ronag ronag changed the title fix: fetch body is not Readable fix: fetch response is not Readable Aug 3, 2021
@ronag ronag force-pushed the fetch-body branch 9 times, most recently from 4355f67 to a9fbcdb Compare August 3, 2021 16:17
@codecov-commenter
Copy link
Copy Markdown

codecov-commenter commented Aug 3, 2021

Codecov Report

Merging #921 (fcd8660) into main (26227a2) will decrease coverage by 0.62%.
The diff coverage is 54.03%.

Impacted file tree graph

@@            Coverage Diff             @@
##             main     #921      +/-   ##
==========================================
- Coverage   94.26%   93.64%   -0.63%     
==========================================
  Files          29       29              
  Lines        2477     2517      +40     
==========================================
+ Hits         2335     2357      +22     
- Misses        142      160      +18     
Impacted Files Coverage Δ
lib/api/api-fetch.js 54.49% <52.89%> (-0.47%) ⬇️
lib/api/index.js 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 26227a2...fcd8660. Read the comment docs.

@ronag ronag force-pushed the fetch-body branch 3 times, most recently from f6e6e95 to 57c8da1 Compare August 3, 2021 16:22
@ronag ronag requested a review from mcollina August 3, 2021 16:22
@ronag ronag mentioned this pull request Aug 3, 2021
39 tasks
@ronag ronag force-pushed the fetch-body branch 2 times, most recently from ae5bffc to 38983ff Compare August 3, 2021 16:35
It's much easier to implement spec compliant fetch API if
we don't try to be node streams at the same time.
Copy link
Copy Markdown
Member

@mcollina mcollina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@ronag ronag merged commit 34cb4c6 into main Aug 3, 2021
@ronag ronag deleted the fetch-body branch October 28, 2021 08:11
KhafraDev pushed a commit to KhafraDev/undici that referenced this pull request Jun 23, 2022
* fix: fetch body is not Readable

It's much easier to implement spec compliant fetch API if
we don't try to be node streams at the same time.

* fixup
crysmags pushed a commit to crysmags/undici that referenced this pull request Feb 27, 2024
* fix: fetch body is not Readable

It's much easier to implement spec compliant fetch API if
we don't try to be node streams at the same time.

* fixup
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants