You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I have quiteReslogger, the entire response object is still logged out.
My use-case is that I need certain logging properties from the request/response to be in the root of the log so that they can be consistent with other non-node services.
I would expect that quiteReslogger would limit what is logged about the response, but it seems that it does not do anything - unless I am misunderstanding how the feature is supposed to work.
Can you provide steps to reproduce? We often need a reproducible example, e.g. some code that allows someone else to recreate your problem by just copying and pasting it. If it involves more than a couple of different file, create a new repository on GitHub and add a link to that.
When I have
quiteReslogger
, the entire response object is still logged out.My use-case is that I need certain logging properties from the request/response to be in the root of the log so that they can be consistent with other non-node services.
I would expect that
quiteReslogger
would limit what is logged about the response, but it seems that it does not do anything - unless I am misunderstanding how the feature is supposed to work.produces this (using pretty logging locally)
The text was updated successfully, but these errors were encountered: