When upgrading to v3.4.0, I noticed that redaction was causing the actual objects being redacted to be mutated, such that values are redacted beyond the scope of the logging.
This will result in the final console.log() statement to print out Printing response { items: [ { name: '[Redacted]' } ] }, showing that the actual value of name has been changed beyond the scope of pino logging. This behavior is not present in v3.3.0.
When upgrading to v3.4.0, I noticed that redaction was causing the actual objects being redacted to be mutated, such that values are redacted beyond the scope of the logging.
To reproduce:
This will result in the final console.log() statement to print out
Printing response { items: [ { name: '[Redacted]' } ] }
, showing that the actual value of name has been changed beyond the scope of pino logging. This behavior is not present in v3.3.0.