Repository navigation
doc: stream state after unpipe is undocumented #4812
Description
Activity
@ronkorving @nodejs/documentation Does this material in the docs adequately address this?
The Readable can switch back to paused mode using one of the following:
- If there are no pipe destinations, by calling the stream.pause() method.
- If there are pipe destinations, by removing any 'data' event handlers, and removing all pipe destinations by calling the stream.unpipe() method.
Oh, there's this too. Not sure this addresses the issue here or not. Does it?
Calling readable.pause(), readable.unpipe(), or receiving "back pressure" will cause the readable._readableState.flowing to be set as false, temporarily halting the flowing of events but not halting the generation of data.
This issue has been inactive for sufficiently long that it seems like perhaps it should be closed. Feel free to re-open (or leave a comment requesting that it be re-opened) if you disagree. I'm just tidying up and not acting on a super-strong opinion or anything like that.
From your quotes, I think the docs are probably quite a bit better now. I'm happy 👍
The documentation doesn't mention whether unpipe leaves the stream in flowing mode, or whether a manual resume is needed. If it could mention that, I think that would be helpful. It would also be good to clarify under which circumstances (eg: always vs. when the last pipe has been removed vs. as-long-as-there-are-data-listeners etc...).