Router options not inherited by default

[jasisk]

This issue is related to krakenjs/kraken-js#281.

If a user enables any of the router-specific options in express, they are not inherited by enrouten-based routes. On the one hand, this is expected behavior given these options don't automatically apply to new Router instances as they're not coupled to any particular app instance. On the other hand, enrouten initializing new Router instances is an implementation detail and the behavior should act more like if routes were registered against the express base router.

The express options that apply to the base router are "case sensitive routing" and "strict routing".

[aredridel]

Definitely inherit from the app. It's all one thing as far as the user can tell.

[totherik]

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, expected behavior.

[totherik]

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