(Feature Request) Named routes

[jneen]

The idea here is to have a Single Source of Truth for my routes. So for example:

app.get('myRoute', '/foo/:bar', function() { ... });
app.routes.myRoute.path(2) // => '/foo/2'
app.routes.myRoute.path({bar: 'baz'}) // => '/foo/baz'
app.routes.myRoute.url({bar: 37}) // => 'http://example.com/foo/37'

Alternatively, app.verb could return a route object, which could be made available through exports. I'd also be happy to work on this feature.

[tj]

sorry I dont think I want this. however you could easily roll your own, view the resource example, I think that could be tweeked to do what you want here.

[jneen]

Fair enough. The resource example doesn't quite cut it, unfortunately, since urls like '/user/3' still had to be hardcoded. I suppose I could put routes on my models, but I'd really like to hook in to the parsing of url wildcards, as in rkh/sinatra-advanced-routes. I'll try my hand at rolling my own for the time being, but I should be able to come up with something a little more general.

Actually, just exposing a method (this is in Connect, I guess) to resolve a path given a route template and keys would be sufficient.

[jneen]

So I've rolled my own in a general fashion - I realized the functionality I wanted is independent of Connect's route resolution. It's up here. Thanks for your patience!

[tj]

cool man :D