TJ
TJ
actually you know what, you're totally right hahaha, I just ran into this myself and it's definitely annoying
I just mean inheriting from the jQuery prototype so I don't have to duplicate any of those methods and dont have to make `.el` public api
hmmm could be that most recent commit that I merged, looks fine to me, ill have to write some tests for that
yeah its a bit tough since certain actions will want some middleware, some will not, which is why in general I'm not a huge fan of rails-ish stuff haha, but...
i dunno, i just dont want it to become more ugly than just using app.get() and friends
that looks ok @flockonus, that's essentially what express-resource middleware would be expanding to
i still feel gross about the api, at this point the resource stuff looks worse than some simple app.VERB calls, i wouldnt mind brainstorming some nicer alternatives
yeah i dont like namespaces either. personally i think there's nothing cleaner or simpler than just listing them out https://github.com/visionmedia/express/blob/master/examples/route-separation/app.js#L24 sure it's a bit verbose, but it's dead simple to...
I guess my point is that these sort of abstractions _always_ get in the way, but I agree we need something
if you break down some of the business logic into middleware you can use the format callbacks quite easily but I dont disagree with what you're saying