-
-
Notifications
You must be signed in to change notification settings - Fork 143
fix: accept passing a FileHandle to createReadStream and createWriteStream
#1077
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
Conversation
…eateWriteStream`
fd option be FileHandle in createReadStream, createWriteStreamFileHandle to createReadStream and createWriteStream
| expect(new StatWatcher(vol).vol).toBe(vol); | ||
| }); | ||
| }); | ||
| describe('.createWriteStream', () => { |
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.
any reason why you've added a test for just createWriteStream, but not createReadStream?
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.
just because they're very similar but sure I can write one for createReadStream
G-Rath
left a comment
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.
awesome, once you've applied Prettier to the test file, we should be good to go!
## [4.14.1](v4.14.0...v4.14.1) (2024-12-02) ### Bug Fixes * accept passing a `FileHandle` to `createReadStream` and `createWriteStream` ([#1077](#1077)) ([af163dc](af163dc))
|
🎉 This PR is included in version 4.14.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Letting this option be a
FileHandlealigns the API with Node.js'sfsmodule.(Split out from #1076 per request)