Skip to content

doc: document next('router') behaviour #1131

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 23, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 24 additions & 0 deletions _includes/api/en/5x/router-METHOD.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,3 +40,27 @@ router.get(/^\/commits\/(\w+)(?:\.\.(\w+))?$/, function (req, res) {
res.send('commit range ' + from + '..' + to)
})
```

You can use `next` primitive to implement a flow control between different
middleware functions, based on a specific program state. Invoking `next` with
the string `'router'` will cause all the remaining route callbacks on that router
to be bypassed.

The following example illustrates `next('router')` usage.

```js
function fn (req, res, next) {
console.log('I come here')
next('router')
}
router.get('/foo', fn, function (req, res, next) {
console.log('I dont come here')
})
router.get('/foo', function (req, res, next) {
console.log('I dont come here')
})
app.get('/foo', function (req, res) {
console.log(' I come here too')
res.end('good')
})
```