[FEATURE REQUEST] Correct stack trace of a guard error in request errored pino-http's log

[artursudnik]

The problem I am facing is similar to those described in this feature request. Despite after using LoggerErrorInterceptor I am getting the correct stack trace of errors thrown from controllers or services when an error is thrown from a guard, it behaves like LoggerErrorInterceptor was not used.

Describe the solution you'd like I am not sure if it is a bug or if additional functionality to be added. Probably this problem is caused by Interceptor not being called at all when application flow is broken on a guard level.

[iamolegga]

can you provide minimal example repo with logs?

[artursudnik]

@iamolegga sure, I'll isolate this

[artursudnik]

@iamolegga I apologize for the delay. Here is this problem reproduced: https://github.com/artursudnik/nestjs-pino-issue.

[mattvgm]

I can confirm this happens to me either. Have you came up with a workaround to it?

[artursudnik]

No, unfortunately, I have not.

[iamolegga]

Does it work properly with the original built-in logger?

[artursudnik]

@iamolegga I need to double-check this. I guess yes though.