While using this extension with carside pattern created libraries we want to hide specific logProperties.
Previously all our carside's logProperties were named in pattern "".
So, when we will be able to filter "our" properties by name pattern - it will much easier to create predefined masking operators per library.
As an example we wanna mask email while sending mesage via SMTP. We can use EmailAddressMaskinjgOperator but it will mask all emails logged in the application, but maybe that some emails are public and can be logged.
While using this extension with carside pattern created libraries we want to hide specific logProperties.
Previously all our carside's logProperties were named in pattern "".
So, when we will be able to filter "our" properties by name pattern - it will much easier to create predefined masking operators per library.
As an example we wanna mask email while sending mesage via SMTP. We can use
EmailAddressMaskinjgOperatorbut it will mask all emails logged in the application, but maybe that some emails are public and can be logged.It is a more generic solution of issue #29 (Feature request - add customMaskingOperator option to items in maskProperties list.)