Closed rayie closed 12 years ago
this was why I broke bodyParser into multipart()
, json()
and urlencoded()
, so that if you want to use formidable directly you can just omit multipart()
. In the near future (or now if you only care about modern browsers) you dont need the server for progress updates anyway, but it would be cleaner to omit multipart() and use formidable directly if you're using events
Sounds good. I'll do that. Thanks.
minor feature request if opts contain keys matching formidable event names such as "progress" and "fileBegin", they are not added as listeners but just plain key/val pairs on form
bodyParser.js (line 157)
Not finding any other hook to the formidable.IncomingForm object, exposed by express, so no other oppotunity to add listeners to it when using app.use(express.bodyParser({...})
Maybe change to this:
??