-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Consistency of method naming #30506
Consistency of method naming #30506
Conversation
referred to as readable.push several other times in transform documentation and also documented under readable, so makes sense to just stick with readable.push
-1 I think it's more confusing this way as it looks more like a typo or copy and paste error. |
In that case, there are 3-4 places in that same section (implementing transform) where it is referred to as readable.push, so those should also be changed to transform.push... |
@nodejs/streams @nodejs/documentation @ronag PTAL |
I’m +-0. But I do agree it should be consistent one way or another. |
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.
lgtm
@mscdex do you still think this should not be changed? Or what would be your suggestion about having this consistent? |
@BridgeAR I'm fine with either leaving it as-is since it should be known that |
Ping @meelash |
@BridgeAR present |
Would you mind updating the doc as suggested by @mscdex? |
Ping @meelash |
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.
lgtm
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.
LGTM
8ae28ff
to
2935f72
Compare
Consistency of method naming referred to as readable.push several other times in transform documentation and also documented under readable, so makes sense to just stick with readable.push PR-URL: #30506 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Landed in 1a9d631 |
Consistency of method naming referred to as readable.push several other times in transform documentation and also documented under readable, so makes sense to just stick with readable.push PR-URL: #30506 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Consistency of method naming referred to as readable.push several other times in transform documentation and also documented under readable, so makes sense to just stick with readable.push PR-URL: #30506 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Consistency of method naming referred to as readable.push several other times in transform documentation and also documented under readable, so makes sense to just stick with readable.push PR-URL: #30506 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
referred to as readable.push several other times in transform documentation and also documented under readable, so makes sense to just stick with readable.push
Checklist