Erik Toth

It may be a blessing in disguise. Gives us a little more latitude to take advantage of better directory layout and improve config. I've put together a [very rough proposal](https://gist.github.com/totherik/3f21469118f8332225cc)...

Yep, re: DI. I was considering using an existing implementation by default and injecting the router itself that way, but I haven't yet found a "lightweight" module, hence the code...

I'm im not sure that simplicity and configurability are mutually exclusive. The request to inject arbitrary objects during initialization isn't the basic, simple use-case here. A smart default of always...

True, but I'm personally not willing to codify`var myvar = arguments[1];` as a desired pattern. :)

Well attaching `config` explicitly so will create a tight coupling between kraken-js and enrouten, something that I'm trying to avoid. The only way to avoid that would be to support...

Does someone want to put together a proposal?

Yeah, I think the fact that new routers are an implementation detail supports the fact that app-level settings should be reflected everywhere. From the developer's perspective it's the most obvious,...

Issue #55 allows for explicit configuration of router settings, but still needs to inherit app values.

This dovetails nicely into #35, specifically [the discussion around swaggerize-express](https://github.com/krakenjs/express-enrouten/issues/35#issuecomment-52441976). I would like to see the two converge on solution since it will be a breaking change either way.

I was more thinking that the traversal implementation be pulled into a separate module that can be reference by both enrouten and swagger. I _think_ that module would then need...