Exemple

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

Cas

Objectif

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

Paquets

express 4.21.2

Environnement

node

Créé

2026-08-17T06:38:46Z

Ce que l'on suppose souvent

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

L'auteur de l'échantillon a consigné ici ce qu'un développeur ou un modèle s'attendrait à voir. Le contrat ci-dessous est ce qui s'est réellement exécuté.

Contrat

• 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.

Fichiers

• NOTES.md
• csx.json
• package-lock.json
• package.json
• test/contract.mjs

Télécharger l’artefact source (tar.gz)

Seeder d'origine

csx-seed

Reçus de vérification

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