Skip to content

Conversation

@Trott
Copy link
Member

@TrottTrott commented Mar 4, 2018

Checklist
Affected core subsystem(s)

doc

@TrottTrott added the doc Issues and PRs related to the documentations. label Mar 4, 2018
@nodejs-github-botnodejs-github-bot added the stream Issues and PRs related to the stream subsystem. label Mar 4, 2018
@Trott
Copy link
MemberAuthor

Trott commented Mar 4, 2018

@mscdex
Copy link
Contributor

mscdex commented Mar 4, 2018

I think it would be better to explain why, because stream.read(n) is certainly a useful feature to have.

Copy link
Member

@gibfahngibfahn left a comment

Choose a reason for hiding this comment

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

LGTM, but +1 to @mscdex 's suggestion.

@Trott
Copy link
MemberAuthor

Trott commented Mar 4, 2018

I think it would be better to explain why

Suggested text, anyone?

@gibfahn
Copy link
Member

Suggested text, anyone?

Yeah that's why it was a non-blocking suggestion (from me at least) 😁 .

@mscdex
Copy link
Contributor

mscdex commented Mar 5, 2018

The text seems to have been added by @jasnell in #6947. Quickly browsing that PR's reviews, it seems @chrisdickinson may have implicitly suggested its inclusion, although no reasoning was given behind the sentiment there either.

I think either the comment should be removed entirely or perhaps a reduced version of the comment should be used instead, one that promotes the use of pipe() (where possible) over manual 'data' event handlers or manual .read() invocations.

@Trott
Copy link
MemberAuthor

Trott commented Mar 7, 2018

Landed in cb5f9a6.

Will follow up on @mscdex's suggestion in a subsequent pull request.

@TrottTrott closed this Mar 7, 2018
Trott added a commit that referenced this pull request Mar 7, 2018
PR-URL: #19124 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
targos pushed a commit that referenced this pull request Mar 17, 2018
PR-URL: #19124 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
@targostargos mentioned this pull request Mar 18, 2018
MylesBorins pushed a commit that referenced this pull request Mar 20, 2018
PR-URL: #19124 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
MayaLekova pushed a commit to MayaLekova/node that referenced this pull request May 8, 2018
PR-URL: nodejs#19124 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
jasnell pushed a commit to jasnell/node that referenced this pull request Aug 17, 2018
PR-URL: nodejs#19124 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
MylesBorins pushed a commit that referenced this pull request Sep 6, 2018
Backport-PR-URL: #22380 PR-URL: #19124 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Ruben Bridgewater <[email protected]>
@MylesBorinsMylesBorins mentioned this pull request Sep 6, 2018
@TrottTrott deleted the in-general-1 branch January 13, 2022 22:48
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docIssues and PRs related to the documentations.streamIssues and PRs related to the stream subsystem.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

@Trott@mscdex@gibfahn@jasnell@cjihrig@BridgeAR@nodejs-github-bot