doc: clarify fromReadable() duck-typed contract#63682
Open
trivikr wants to merge 1 commit into
Open
Conversation
Document that duck-typed readable inputs must provide off() in addition to read() and on(), matching the cleanup behavior in the implementation. Signed-off-by: Kamat, Trivikram <[email protected]>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Clarify the documented duck-typed contract for
stream/iterfromReadable().The implementation removes its internal
readablelistener withoff()duringcleanup, so duck-typed readable inputs need to provide
off()in addition toread()andon().Source code:
node/lib/internal/streams/iter/classic.js
Line 195 in 9e58d9d