-
Notifications
You must be signed in to change notification settings - Fork 24
fix: remove credentials from stacktrace #18
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
Conversation
444cd8d
to
03246e0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
* the end user to debug / store stack frames even | ||
* when a retry error does not happen. | ||
*/ | ||
console.log('Retryable failure', stackFrameWithoutCredentials(stackFrame)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For now this is probably fine, but we might want to extract this into a Logger
class that the user can swap for something custom (e.g. writing to a file or server instead of to the console).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea, I created a ticket
Co-authored-by: Clément Vannicatte <20689156+shortcuts@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
Remove credentials from stackTrace and print stackFrame when a retry happen.
There is no true logger for now so it's just
console.log