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

Support readstreams #360

Closed
DylanPiercey opened this issue Nov 7, 2015 · 22 comments
Closed

Support readstreams #360

DylanPiercey opened this issue Nov 7, 2015 · 22 comments

Comments

@DylanPiercey
Copy link

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.

@reinhardholl
Copy link

+1

This is also something I am very interested in!

@Houfeng
Copy link

Houfeng commented May 24, 2016

+1

2 similar comments
@Houfeng
Copy link

Houfeng commented May 25, 2016

+1

@Houfeng
Copy link

Houfeng commented May 25, 2016

+1

@tunnckoCore
Copy link
Member

tunnckoCore commented Jun 2, 2016

This also will allow using all gulp plugins. 👍

@tunnckoCore
Copy link
Member

Definitely for some of next (major) releases. Marking it as feature.

@miafan23
Copy link

+1

@GrosSacASac
Copy link
Contributor

soon

@omerdn1
Copy link

omerdn1 commented Dec 16, 2019

This would be awesome!
For now, how can I turn a writestream file into a readstream file while keeping all of its attributes?

@tunnckoCore
Copy link
Member

@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.

@tunnckoCore
Copy link
Member

@all-contributors please add @DylanPiercey for ideas

@allcontributors
Copy link
Contributor

@tunnckoCore

I've put up a pull request to add @DylanPiercey! 🎉

@tunnckoCore tunnckoCore pinned this issue Jan 31, 2020
@guoyibj
Copy link

guoyibj commented Mar 17, 2020

@DylanPiercey Do you have plans to implement this?

@tunnckoCore
Copy link
Member

tunnckoCore commented Mar 17, 2020

@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.

@GrosSacASac
Copy link
Contributor

I am busy in other projects in the near future

@GrosSacASac
Copy link
Contributor

Does #666 fix this issue ?

@tunnckoCore
Copy link
Member

Basically yes. Partially. Yes and no.

Should think more about it 🤣

@QaisKhanFakhree
Copy link

+1

@GrosSacASac GrosSacASac unpinned this issue Aug 5, 2021
@GrosSacASac
Copy link
Contributor

Did you think about it ?

@tunnckoCore
Copy link
Member

wow.. whole year and one month.. 😞

@GrosSacASac, well, the PR is merged, isn't it on v3 already?

@GrosSacASac
Copy link
Contributor

V2 and v3

@tunnckoCore
Copy link
Member

Ah yea. So, we can close that then haha 🤦‍♂️😆

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants