TJ
TJ
I just use the app.VERB methods, looks way better IMO. express-resource is ok but these are all leaky abstractions really, express-namespace is gross I kinda wish I never wrote that...
you can still keep things DRY without this sort of abstraction, and being DRY is not a good choice when it means being using leaky abstractions that you can't back...
@panta yeah all leak for sure, to me the important part is that they're easy to back out of without coding in strange hacky work-arounds, which is what this module...
plus even with regular routes you can do simple stuff like: ``` js app.all('/admin*', authenticate); app.get('/admin/stats', ...); ``` etc, vs a huge map of middleware which is a bit of...
just with regular callbacks, though we don't have much CRUD, I can understand the appeal for apps with tons of it
yeah we're mostly client as well, just a very small amount of basic CRUD
@dikbrouwer details the structure a little bit but doesn't go into config etc http://t.co/tYsbAx6t
the route itself does that already, that's like going to an express route that does a res.redirect() to itself
but if that route is invoked you're already displaying that page, so there's no need to page() cyclicly. There's `page.replace(path)` if you're rewriting the path or doing something weird, that's...
I guess I don't get why there's one method for two things, howcome it cant be say `note.render()` (or whatever) and `note.select()` to programmatically do your page() call, but then...