-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redact sensitive struct fields on inspect #181
base: master
Are you sure you want to change the base?
Redact sensitive struct fields on inspect #181
Conversation
This pull request has been automatically marked as "stale:discard". If this pull request is still relevant, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize reviewing it yet. Your contribution is very much appreciated!. |
Bump |
This pull request has been automatically marked as "stale:discard". If this pull request is still relevant, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize reviewing it yet. Your contribution is very much appreciated!. |
bump |
This pull request has been automatically marked as "stale:discard". If this pull request is still relevant, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize reviewing it yet. Your contribution is very much appreciated!. |
bump |
Hi,
Thanks for this great library.
Noticed these fields end up on our app's logs and/or error tracking reports in cases like e.g.
MatchError: no match of right hand side value: %OAuth2.Client{..., client_secret: "<secret>", ...}
when having match errors when doing stuff likeWe temporarily fixed this on our app's end by writing
But maybe you wanted to consider adding it to the package?
Thanks.