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.
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
stream: fix
isDetachedBuffer
validations inReadableStream
#44114stream: fix
isDetachedBuffer
validations inReadableStream
#44114Changes from 6 commits
e5e32c0
50c7728
6f6ba3e
782c71a
e44effa
6fd3ea1
0cc34f4
fe816cd
58da0d8
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Non-blocking comment: this change is fine in context of this PR, but it probably should be rewritten in a follow-up.
It would be better if
is*
functions always returned boolean without throwing. If we want to throw,validate*
function is preferable.Since either
true
orfalse
won't make sense if provided value is not a buffer, it looks like an acceptable temporal solution.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.
Indeed, it looks better to follow the coding convention.
I updated the util using
assert
instead, since, as you mentioned, eithertrue
orfalse
won't make sense if a provided value is not a buffer. We can guarantee a passing value is a buffer since it's internal util. PTAL.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.
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.