You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the description of the path & callback arguments is also applicable to router.all, router.METHOD, and router.use, but I wasn't 100% sure.
Since the method signatures (in the headings, e.g. http://expressjs.com/en/4x/api.html#app.all) have callback [, callback ...] , I wonder if we need to specify "A series of middleware functions (separated by commas)." since that's implied by the signature? Maybe it's clear either way? Or perhaps we should just have callback(s) in the signature?
This discussion was converted from issue #707 on August 02, 2025 18:31.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
From #701:
I think the description of the path & callback arguments is also applicable to
router.all
,router.METHOD
, androuter.use
, but I wasn't 100% sure.Since the method signatures (in the headings, e.g. http://expressjs.com/en/4x/api.html#app.all) have
callback [, callback ...]
, I wonder if we need to specify "A series of middleware functions (separated by commas)." since that's implied by the signature? Maybe it's clear either way? Or perhaps we should just have callback(s) in the signature?Beta Was this translation helpful? Give feedback.
All reactions