-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
Do not crash if nested plugin does not call next #252
Do not crash if nested plugin does not call next #252
Conversation
Signed-off-by: Matteo Collina <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense
test/plugin-timeout.test.js
Outdated
app.ready((err) => { | ||
t.ok(err) | ||
t.equal(err.fn, one) | ||
t.equal(err.message, message('one')) // TODO: should be 'two' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So this means we should in the future be able to show that two failed right?
Signed-off-by: Matteo Collina <[email protected]>
@gurgunday @ivan-tymoshenko PTAL. I fixed the error message too. |
Fixes fastify/fastify#5410
Checklist
npm run test
andnpm run benchmark
and the Code of conduct