Ben Augarten

I dislike that it would be exposed as `?location_nocase` and `location_regex=/boise/i` I'm in the middle of a rewrite, in which filters underwent a major refactory. I think it'll be easier...

Hey there, So. For custom routes, we don't do any preprocessing -- so, you can access the :id by doing `req.params.id` -- so you will have to query mongoose yourself...

Sounds interesting. I was going to look into factoring it out, but if it already exists, then that's even better :) Thanks for the heads up :beers:

Yes, please. That would be wonderful I'm mid rewrite, but the API for filters will stay the same

Under the covers, we use `findByIdAndRemove` on the model to remove the object from the collection. The mongoose documentation specifies that this is one of the operations that does not...

What other metadata would you like included? I see this best bundled as a separate module that does automaticaly adds an afterAll that wraps the response data with the calculated...

This is better accomplished using HTTP Headers, similar to the GitHub API -- https://developer.github.com/guides/traversing-with-pagination/ Do you have any metadata that you actually would like included in the response body?

I don't think this makes sense to bundle with node-restful because there are many ways to accomplish sending pagination info back to a client. You could accomplish this by adding...

Actually... I've thought about this a bit more (especially viewing your example). Maybe pagination info is something that could be extracted/provided more easily by the library. Possibly not rendering it...

You could use a selection algorithm to get O(n) median calculation, it would just eat up more memory... do you test the graph for cycles?