-
Notifications
You must be signed in to change notification settings - Fork 27
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
interop with pino-http by setting res.err instead of calling log.error #20
base: master
Are you sure you want to change the base?
Conversation
Benchmarks (master) benchmarks/pino-error-server.js
(PR) benchmarks/pino-error-server.js
(master) benchmarks/pino-extreme-server.js
(PR) benchmarks/pino-extreme-server.js
(master) benchmarks/pino-server.js
(PR) benchmarks/pino-server.js
|
Leaving a note for myself that I didn’t confirm a test case exists for ensuring the status is correctly captured when using ctx.throw |
b4d5329
to
cdfb980
Compare
As it turns out, we only needed to assign The Error instances created by http-errors assigns both Is it possible to customize the err serializer to pick |
Yeah ... this being so outdated is (I think) causing the pino |
@davidmarkclements Is this likely to get merged any time soon? |
cdfb980
to
d138fea
Compare
@Fdawgs it has been a very long time, since I opened this, and I'm not actively using the package, but I did the rebase, so that this PR now just addresses the issue of thrown errors being logged in duplicate. 🤞 |
err.status as recognized by pino-http
benchmark
fixes #19