-
-
Notifications
You must be signed in to change notification settings - Fork 681
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
Support readstreams #360
Comments
+1 This is also something I am very interested in! |
+1 |
2 similar comments
+1 |
+1 |
This also will allow using all gulp plugins. 👍 |
Definitely for some of next (major) releases. Marking it as |
+1 |
soon |
This would be awesome! |
@omerdn1 I don't think this much sense if possible in Node Streams. Here we are talking about from when the upload happens to be readable streams, so then later you can pipe it to transform or writable. Currently it's directly writable and written to the disk. |
@all-contributors please add @DylanPiercey for ideas |
I've put up a pull request to add @DylanPiercey! 🎉 |
@DylanPiercey Do you have plans to implement this? |
@guoyibj yup. @GrosSacASac probably can do that, but he maybe waiting me to release v2 which I can't get to, but v2 will be in coming for sure. |
I am busy in other projects in the near future |
Does #666 fix this issue ? |
Basically yes. Partially. Yes and no. Should think more about it 🤣 |
+1 |
Did you think about it ? |
wow.. whole year and one month.. 😞 @GrosSacASac, well, the PR is merged, isn't it on v3 already? |
V2 and v3 |
Ah yea. So, we can close that then haha 🤦♂️😆 |
Currently (As far as I can tell) formidable exposes files as write streams and saves them to the disk automatically. It would be handy if it could also have an option to expose the files as read streams so that the files are not persisted to the disk until read.
Formidable could then listen for the response to end and close and (unused) read streams.
The text was updated successfully, but these errors were encountered: