Matteo Collina

I would even recommend against using the global cache (for mostly the same reason.

I will reply bottom up, as it's the simplest solution: > I saw that with pino v7, you no longer need to use pino.final. Does that mean I don't need...

Thanks for your feedback, this is gold. It will take a while to get us through it all - we will update the docs with some more clear "best practices".

> Thank you, feel free to update documentation at your own pace! Not really but if you would like to send PR it would be mostly welcomed.

> Sorry, just wanted to see if the issue has been long-forgotten and was out of your mind. If you’re still working on it, that’s fine I'm not working on...

The best approach is to develop a custom transport that make it suit your needs, see https://getpino.io/#/docs/transports.

> At this point the only way I see it is to parse the object and change it to removes all the keys at nesting level > MAX_DEPTH, before passing...

cc @kibertoad

pino relies on prototypical inheritance for implementing the child loggers, so we can't provide a prototype to extend. Maybe an interface?

Maybe add a test for this use case?