Christopher Watford

So I've cobbled together what could be the base for this as a [gist](https://gist.github.com/sixlettervariables/0c8c9589c7c0e20c7335). It _appears_ to match the behavior of a hybrid `expresss-enrouten`/`swaggerize-express`. It supports an options hash which...

~~The downfall of this approach with enrouten, is [express doesn't let you get the params from your parents in the stack](https://github.com/strongloop/express/issues/2153). I had forgotten this until attempting to convert express-enrouten...

I've completed my conversion to order routes with `index.js` first, use swaggerize-express style file naming, and be compatible with the old style structure (minus the order of resulting routes). The...

This is currently in place (not only in enrouten, but preserved in my update). On Thu, Aug 21, 2014 at 1:15 PM, Trevor [email protected] wrote: > I understand the use...

When you stare at directories of route handlers all day, it makes your eyes water ("there has got to be a better way!"). The one problem this brings with it...

A nasty side effect seems to be `router.param()` no longer appears to work as it only affects the paths at the current level.

Yep! On Jul 12, 2017 18:22, "Gabriel Csapo" wrote: > @sixlettervariables would you be > able to rebase your changes? > > — > You are receiving this because you...

Rebased.

I do not actively maintain any nodejs projects anymore, and my free time is lacking. If someone would like to pick this up and fix/extend it that'd be great.

If _slightly_ more deterministic route ordering is what he'd like, I've started that in PR #47.