Router: add parameter handling to middleware

[defunctzombie]

Middleware (.use) can now specify parameter arguments to trigger
Router.param loading. This is handy if you want to .use additional
routers but need to load certain objects before the mounted middleware
runs.

This will resolve #696

[ismailarilik]

I cannot still use route parameters with app.use on Express 4.16.2.

I have a statement like this:

app.use('/course-sessions/:courseSessionId/chapter-sessions', chapterSessionsRouter)

And, in chapter sessions router:

// Index.
router.get('/', ...resource.indexMethods)

When I got '/course-sessions/0/chapter-sessions/', I have 404.

Then I am trying a statement like this:

app.get('/course-sessions/:courseSessionId/chapter-sessions', ...chapterSessionResource.indexMethods)

Now I have the result I want. So route parameters still don't work with app.use. Please fix me if I am wrong but didn't this pull request solve this issue?

[paulrad]

Try to invoke your Router like this

const router = new Router({mergeParams: true})

[remotevision]

Try to invoke your Router like this

const router = new Router({mergeParams: true})

Did this work for others? I did not see a difference and still receiving a 404.
"express": "^4.16.4"

/routes/index.js
app.use('/index', indexManager);

/routes/indexManager+v1.js

const router = new express.Router({ mergeParams: true });
module.exports = router;

router.put('/:id', (req, res) => {
  res.send('Got a PUT request at /index');
});

I also tried adding this per their example, but still returns a 404.

router.param('id', function (req, res, next, value) {
  console.log('CALLED ONLY ONCE with', value);
  next();
});

EDIT:
Never mind, this was a Firebase Function routing problem for me. Anyone else using Firebase Functions, simply having a rewrite of just /path is not sufficient for url params. Need to have /path/**