Ran
|
Files
8
|
Run time
1s
|
Badge
Embed ▾
README BADGES
|
travis-ci
<a href="https://github.com/zendframework/zend-expressive-router/commit/<a class=hub.com/zendframework/zend-expressive-router/commit/da8c7438c6914bb54bf120b8d89fa5f08b5e55df">da8c7438c<a href="https://github.com/zendframework/zend-expressive-router/commit/da8c7438c6914bb54bf120b8d89fa5f08b5e55df">">Revert &quot;Clarify that HEAD and OPTIONS should ALWAYS be allowed" This reverts commit </a><a class="double-link" href="https://github.com/zendframework/zend-expressive-router/commit/<a class="double-link" href="https://github.com/zendframework/zend-expressive-router/commit/a81bf26435015cc28f2bc411460488e31ec2fd8f">a81bf2643</a>">a81bf2643</a><a href="https://github.com/zendframework/zend-expressive-router/commit/da8c7438c6914bb54bf120b8d89fa5f08b5e55df">. Per #28, auto-adding the HEAD and OPTIONS methods to each route causes `Zend\Expressive\Application` to raise an exception; additionally, when working on zendframework/zend-expressive-fastroute#24, I noticed that tests broke due to duplicate paths having the same HTTP method defined; adding HEAD and/or OPTIONS was causing adding routes with GET to result in exceptions. There are other ways for the routers to accommodate this, which can be done with the `implicitHead()` and `implicitOptions()` methods of the routes themselves, or by opportunistically checking for any method to match against a given path.
98 of 98 relevant lines covered (100.0%)
6.09 hits per line
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
---|