Skip to content
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

Documentation/Add 'close' events to fs.ReadStream, fs.WriteStream, etc per Issue #6484 #6499

Closed
wants to merge 8 commits into from
Prev Previous commit
Next Next commit
Fix/Changed 'close' event from 'fs.ReadStream' to 'fs.WriteStream'
  • Loading branch information
Jenna Vuong committed May 1, 2016
commit 439df4bc52d923b1daa3d8877b5f61a9f8dc94e7
2 changes: 1 addition & 1 deletion doc/api/fs.md
Original file line number Diff line number Diff line change
Expand Up @@ -244,7 +244,7 @@ Emitted when the WriteStream's file is opened.

### Event: 'close'

Emitted when the ReadStream's underlying file descriptor has been closed. Comes from fs.close() method.
Emitted when the WriteStream's underlying file descriptor has been closed. Comes from fs.close() method.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nodejs/streams can we please check this? I thought 'close' was for Readable and 'finish' was for 'Writable'. However, in 'fs' we have 'close' for 'Writable' as well. I do not think custom stream events are that helpful in understanding, so maybe we might want to rationalize this (or document it in streams).


### writeStream.bytesWritten

Expand Down