-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
Allowing custom error messaging on unsupported encoding #88
Conversation
Merge pull request fastify#86 from j-windsor/master
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.
LGTM
Co-Authored-By: Denis Fäcke <serayaeryn@gmail.com>
Co-Authored-By: Nicola Dal Maso <niktekusho@users.noreply.github.com>
I feel good about getting this merged now! |
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.
Sorry, I'm finicky 😅
I would keep the usual request, replay
order since it is common for all these kind of callback 👍
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.
LGTM with a style nit
Co-Authored-By: Matteo Collina <matteo.collina@gmail.com>
Co-Authored-By: Matteo Collina <matteo.collina@gmail.com>
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.
Landed in v1.1.0, thanks!
created new function in the options to allow users to specify a custom response when the encoding is unsupported.
I could not follow the original design of using the reply.send() function in the callback because you can't call that function in the onSend hook.
Checklist
npm run test
andnpm run benchmark