resource-router-middleware

Overview Currently all the keys are just functions (ie. create, read). You can have a case where auth is required for creating a resource but not reading it. You can't add middleware to specific controllers. The old usage would still work, where create is a function. Example:

import resource from 'resource-router-middleware'; import multer from 'multer'; let uploads = multer({ dest: 'uploads/' }); export default resource({ middleware: [ uploads.single('avatar'); ], // then use it in a route: create({ body, files }, res) { console.log(files); res.json(body); } }); (Reference from #6) I'm trying to use uploads.single() my parameter and form name has matched but my console.log(files); return undefined. How can I Accept a single file with the name fieldname?

Feature request There are cases where the user may not need to preload resource data by and just perform the action (ex: DELETE, PATCH, PUT) on the resource itself. A good example of this is a call to a database using a defined (non-public) token. Use example Now, this could be handled by creating a separate router middleware specific to this use-case. But in the effort to consolidate routes for a given , while taking advantage of actions and injection provided by this library, it would be nice if it supported both scenarios. Code update Currently, this expression prevents the route from being loaded when the resource doesn't exist. A simple solution to this would be to make this value optional and rely on to determine whether this value should be defined (as it does already) and how it should be handled. Let me know your thoughts on this?