Feature: Extendable fileUploader #248

[dotMortis]

Feature: Extendable fileUploader #248

[cdimascio]

@Haruki-Mortis this looks pretty good.
that said, i'm still mulling over whether this is the right way to handle it
can you describe again why we need pre and post middleware?

also, please let me know if you have any thoughts on how this could be handled without requiring pre and post middleware. i understand this may not be possible and (if possible) may require a significant overhaul. that said, now that you've been in the code, you likely have a decent idea of what is and isn't possible. im hoping you might also have thoughts on how file upload might reimagined, so that it can be simpler

thanks a lot for this PR.

[setaman]

@Haruki-Mortis @cdimascio I don't want to be bound to multer.any() as well and want to be able to provide custom uploader. My approach to implementing this is really simple. We can simply extend the fileUploader with an another prop, let's say uploadHandler, that is a function returned by multer().single("image") for example. Then instead of:

multer.any()(req, res, next) {...}.

we can do:

options.multOpts.uploadHandler(req, res, next) {...}

This is straightforward to implement and gives the user the ability to use multer without restrictions. I have already implemented and tested this approach exemplary, works fine. What do you say? Is this worth a PR?

[cdimascio]

@Haruki-Mortis good idea. this will provide good flexibility

[devthejo]

Hello, any news on this ?
I would like to use a custom implementation of multer too, to allow use of upload without multipart, like described here https://swagger.io/docs/specification/describing-request-body/file-upload/
Let me know if a new PR is welcome on this.
PS: Thanks for this great tool you built !

[cdimascio]

@devthejo I support the idea and welcome PRs.