-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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: update comment to indicate unused API #32808
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
destroy w/ callback was previously used by node core. This is no longer the case and the comments should reflect this to avoid confusion.
My mistake, there was one last use case I missed. #32809 |
lpinca
approved these changes
Apr 13, 2020
👍 for deprecating it and then removing it. |
ronag
added
the
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
label
Apr 14, 2020
ronag
requested review from
AndreasMadsen and
mcollina
and removed request for
AndreasMadsen
April 14, 2020 19:37
mcollina
approved these changes
Apr 15, 2020
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
I think we could even remove it in a semver-major change.
ronag
added a commit
to nxtedition/node
that referenced
this pull request
Apr 15, 2020
destroy(err, cb) was an undocumented API which was previously used internally by core modules. However, this is no longer the case and it should be possible to safely remove this. Refs: nodejs#32808
4 tasks
ronag
added a commit
that referenced
this pull request
Apr 16, 2020
destroy w/ callback was previously used by node core. This is no longer the case and the comments should reflect this to avoid confusion. PR-URL: #32808 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Landed in 15cc2b6 |
MylesBorins
pushed a commit
that referenced
this pull request
Apr 17, 2020
destroy w/ callback was previously used by node core. This is no longer the case and the comments should reflect this to avoid confusion. PR-URL: #32808 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
author ready
PRs that have at least one approval, no pending requests for changes, and a CI started.
stream
Issues and PRs related to the stream subsystem.
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.
destroy w/ callback was previously used by node
core. This is no longer the case and the
comments should reflect this to avoid confusion.
We briefly discussed making this API public. I'm still good with that but it would require the
if (destroyed)
branch to usestream.finished
. Though if and until then this PR updates the comments to reflect the current state of things. The use ofdestroy(err, cb)
has been refactored away in recent PRs.Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes