Adding pre from request object about laabr

[felixheck]

Hi @JSteunou — thanks for opening this issue, really appreciating it 👍

That's true, req.pre is not included in laabr's req object and that's simply because it's not in hapi-pino's req object. So let me create a PR for hapi-pino. After it's merged, I'll release a minor update where you get access to pre within the request/response templates, like

{ awesomePreHandler: pre[key] }

Does this work for you?
Thanks a lot for your feedback.

[felixheck]

But TBH: I'm not sure if it will be merged since it's a massive workaround on hapi-pino side

[JSteunou]

Yep I did dig a little and found out it was directly related to pino & hapi-pino serializer :(

I worked around it by adding another preHandler at the end of all my preHandlers that does nothing more than request.log and using some :message[field=msg] but I am not very proud of it because it adds a specific line of log instead of adding more data into request / response log.

[felixheck]

Related: hapijs/hapi-pino#73

[felixheck]

Hmm..I'm currently struggling with explaining a good use case.
I mean the responses of such prehandlers are like a payload and you wouldn't expect to print the payload automatically, right?

I would use a request.log(['info', 'pre'], somestuff) tbh.
Can you explain your use case in detail?

[JSteunou]

For example loading user / profile info in a preHandler, making request.pre.profile available for every handlers, and logging profile.id for some request / endpoint to help debug / trace.