Documentation and Case Sensitivity

[shellscape]

One of the things that threw me for a loop while giving the redact feature a spin in pino was the fact that it's not documented whether or not the redaction paths are case sensitive.

It turns out that they are. That makes it extremely burdensome to construct a comprehensive list for redacting logs across a wide organization. Consider socialsecuritynumber and the variations possible:

socialsecuritynumber
socialSecuritynumber
socialsecurityNumber
socialSecurityNumber

The argument here might be "well this is a code quality issue that should be caught or prevented," and that would be well justified. But across large orgs with varying teams, varying levels of skill, oversight, and caring, asserting code quality isn't a reasonable assertion.

First and foremost, the documentation needs to be updated to reflect the current state - paths are case-sensitive.

I'd love to see some consideration given to allowing for the search to be case-insensitive.

[mcollina]

Would you like to send a Pull Request to address this issue? Remember to add unit tests.

[shellscape]

(for reference only, cross-linking my reply here pinojs/pino#915 (comment) which is relevant to the ask)