silvermine / lambda-express / 40 / 4

99%

master: 98%

push

travis-ci-com

<a href="https://github.com/silvermine/lambda-express/commit/<a class=hub.com/silvermine/lambda-express/commit/2799ecf3f3f2c30d0b613d34892e12463a775606">2799ecf3f<a href="https://github.com/silvermine/lambda-express/commit/2799ecf3f3f2c30d0b613d34892e12463a775606">&quot;&gt;Revert path-to-regexp to same version Express uses

There were a few differences between the version Express uses (0.1.7)
and the version we started out using (3.0.0). Notably, the support for
`/*` was drastically different. Since that one pattern will be used so
frequently, it didn&amp;#39;t seem worth trying to maintain that difference as
it would negatively impact developers familiar with the `/*` pattern.

There was also a difference in the support of modifiers indicating how
many times a named parameter could appear (e.g. `/:path+` for params
like `/some/directory/and/file/path`).

The differences were clearly explained on the [path-to-regexp
homepage][1], but I originally thought it might be worth accepting those
differences or working around them. This doesn&amp;#39;t seem feasible or worth
it, though.

[1]: https://github.com/pillarjs/path-to-regexp/blob/</a><a class="double-link" href="https://github.com/silvermine/lambda-express/commit/<a class="double-link" href="https://github.com/silvermine/lambda-express/commit/4eee1e15ba72d93c996bac4ae649a846eb326562">4eee1e15b</a>">4eee1e15b</a><a href="https://github.com/silvermine/lambda-express/commit/2799ecf3f3f2c30d0b613d34892e12463a775606">/Readme.md#compatibility-with-express--4x

177 of 180 branches covered (98.33%)

Branch coverage included in aggregate %.

345 of 349 relevant lines covered (98.85%)

290.15 hits per line