| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
s/ambigious/ambiguous/ in commit message |
Sorry, something went wrong.
|
Not sure what you meant. But I'm guess it's the misspelling. Fixed. |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
cc @mafintosh
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
Sorry, something went wrong.
PR-URL: #29664 Reviewed-By: Minwoo Jung <minwoo@nodesource.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
|
@ronag I guess this depends on other PRs that need backporting first? This currently causes conflicts that are not obvious to resolve. Would you be so kind and check if other PRs need backporting first and add that as well / open a backport if you think that's useful here? |
Sorry, something went wrong.
|
This is probably about to be reverted in #29717 (comment). I will look into backporting this if/when this becomes relevant again. |
Sorry, something went wrong.
|
quick ping re: backport |
Sorry, something went wrong.
PR-URL: nodejs#29664 Reviewed-By: Minwoo Jung <minwoo@nodesource.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
PR-URL: nodejs#29664 Reviewed-By: Minwoo Jung <minwoo@nodesource.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
|
@MylesBorins In view of 8c60685#diff-009356850b536cab27b019ba8ad15e72 are you sure this should be backported? |
Sorry, something went wrong.
|
Seems like it shouldn't |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This cleans up some ambiguous code. I don't believe this actually causes any observable change of behaviour.
writable, readable is supposed to indicate the type of the stream, which does not change... this PR makes the code less confusing
Checklist