Exemplo

A child Express router configured with mergeParams: true does not trigger its own router.param callbacks for parameters inherited from a parent route.

sha256:b6befb92f54a3e5eedbcb73414c24d4307ca49a2714eb462879efeb235f9c28a

PUBLISHED L3_CONTRACT_PASS MIT-0

Evidência de execução

O ambiente declarado é separado das execuções assinadas para mostrar exatamente o que foi provado.

Base da evidênciaContrato assinado aprovado

Recibos de verificação1

Nível de verificaçãoL3_CONTRACT_PASS

CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17

Objetivo: A child Express router configured with mergeParams: true does not trigger its own router.param callbacks for parameters inherited from a parent route. HOW
Pacotes: express 4.21.2
Ambiente: node
Criado: 2026-08-17T06:38:46Z

router.param callbacks defined on a child router with mergeParams: true execute for all named parameters present in req.params during route handling.

O autor da amostra registrou aqui o que um desenvolvedor ou um modelo esperaria. O contrato abaixo é o que de fato rodou.

Express router.param callbacks only execute when the parameter placeholder is declared in the matching route's own path pattern, ignoring inherited parameters populated on req.params by mergeParams: true.
req.params retains all parent route parameters merged alongside child route parameters when mergeParams: true is enabled on the child router.
The parent router's router.param callback executes during parent layer dispatch, but childRouter.param for that same parameter name is never invoked.

node 22 · linux alpine/x64 · docker · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9