panates / opra

86%

main: 86%

Pull #128

github

feat(nestjs-http): Add getOpraContext() for guards and interceptors

A guard runs before the handler, and it is the handler that settles
which of a request's contexts is the active one. Until then
`req.opraContext` holds whichever module's middleware ran last, so in an
application with two modules a guard setting `ctx.user` wrote it to the
other API's context and that API's handler saw no user. Exactly one of
the two modules worked, and which one was a matter of middleware order.

Everything needed to resolve this was already exported — the adapter
metadata on the controller class and `getRequestContext` — but only as
parts, leaving every application to join them itself and to know the
metadata key. `getOpraContext(executionContext)` is that join: it asks
the controller class which adapter owns the route and returns the
context that adapter built, falling back to the active context for a
route that is not an OPRA controller's.

With a single module it returns what `req.opraContext` would have, so it
is the right thing to reach for either way.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

4822 of 6175 branches covered (78.09%)

Branch coverage included in aggregate %.

77 of 78 new or added lines in 3 files covered. (98.72%)

41154 of 47295 relevant lines covered (87.02%)

317.14 hits per line