Feature Request?: Access request object inside StorageManager

[vivia1990]

Hi,
First thank you for the great package!

I've migrated to transmit from multer, because i had some problems with it.
One (imho) great thing of multer was the ability to access the Request object inside the custom Storage object, because it was a middleware. In this way I could easily manage where to store the files, due to some useful domain data in the Request.

Now my workflow is

• use the default manager to store file in a temp directory
• move the files, after the parseAsync, to the definitive path

If it was possible to access the request object in some way inside the Manager,I would have to do IO only one time.
Is my workflow wrong? Or may this be a useful feature to add?

Thank you, and let me know.

[alexy4744]

Hi, can you let me know what the use-case is for accessing the req object? Adding support for accessing the express req object would violate the Transmit's framework agnostic principles. What can be added instead is the http.IncomingMessage object as it is the underlying type to all web frameworks in node.

[vivia1990]

My use case is that I need to save some files to different paths based on the request fields at the moment. ( but it could be an http header to)
Now I can't do that because in the manager i have only access to the File object.
http.IncomingMessage would be good, because from that I think I can get the request headers, at least.

The Express Request/Response objects were good, because from them I had the direct access to the request, and the parsed fields, by multer, of the multipart/form-data.
Another idea that comes to my mind, could be to have access to the parsed fields into the manager handleFile, remoFile methods. But I took a quick look at the code and busboy parses the fields and the files apart. So this seems a little hard to implement. If it makes sense.

Hope I've been clear, thank you.