Ben Augarten

@matheo Can you add tests that show the intended behavior working correctly?

I think this is fixed in 72c298d153a430f2d03f849a33828e3633093f02, released as version 0.2.5 Let me know if you have any trouble

Published another version, 0.2.6, which contains the fix

Thanks! :) Currently, there's no way to override the handler of specific endpoints. You can paginate the data manually using the parameters `limit=?&skip=?` You can limit the fields by either...

Hey @sharathm Glad you like the module. I must have missed this issue. The additional arguments used to be supported before I refactored how the middleware gets set up. In...

I suppose that would be possible to populate the model, but I would have to think it over more. For now, I added support for registering multiple handlers for a...

I suppose this really reduces to #25 ``` js resource.before(*, function(req, res, next) { if (!authorized(req)) return next(err); next(); }); ``` But we can make this API explicit ``` js...

First, you could just do ``` js function filterAccess(req, res, next) { req.quer = req.quer.where('owner', someuserIdFromSession) next() } ``` Next, you could solve this using a custom route ``` js...

I thought you wanted to populate request data from session data. Authorization you can currently do on select routes ``` js resource.before('get', function(req, res, next) { if (!authorized(req)) { return...

We actually have tests that assert they're only called once. Part of the problem might be that you're registering the same function `fn`? That function will get called twice --...