pillarjs / router / 39983648950

99%

Build Type

push

github

Committed by web-flow

Commit Message

feat: expose the matched route pattern on the tracing context (#207)

* docs: document reading the route pattern from the tracing context

* feat: expose the matched route pattern on the tracing context

* fix: keep traced route patterns scoped to each request

Layer instances are shared across requests, so reading a matched pattern
after asynchronous parameter processing can pick up another request's
pattern or lose it after a non-match. Nested routers can also leave their
pattern on handlers that resume in the outer route.

Let Layer.match optionally return the registered pattern while preserving
its existing boolean behavior. Capture the pattern on req before running
parameter callbacks, and restore the parent value alongside the other
router state when a nested router returns. Tracing then reads from one
request-local source instead of mutable state on a shared Layer.

Pattern capture and restoration use synchronous property access and the
existing restoration callback. Route.dispatch and handler signatures stay
unchanged, with no additional asynchronous context mechanism or per-layer
callback allocation.

Cover concurrent requests, nested router returns and errors, parameter
callbacks that invoke routers, and string, array, RegExp and empty patterns.

Validation: 768 tests passing, npm run lint, and npm run test-types.

---------

Co-authored-by: Sebastian Beltran <bjohansebas@gmail.com>

Coverage Stats

15 of 15 new or added lines in 3 files covered. (100.0%)

1 existing line in 1 file now uncovered.

486 of 491 relevant lines covered (98.98%)

46065.97 hits per line