-
Notifications
You must be signed in to change notification settings - Fork 19
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
Allow disabling stack traces, add test. #192
Conversation
03bd2a9
to
f3e19db
Compare
Signed-off-by: Tommy Carpenter <[email protected]>
f3e19db
to
e8f3c18
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.
We would want to ensure existing service behavior is not changed. Some small changes could allow that to happen.
Additionally, more information about the reason for your changes in your pr would be appreciated.
Signed-off-by: Tommy Carpenter <[email protected]>
ac11bc8
to
d46348e
Compare
Signed-off-by: Tommy Carpenter <[email protected]>
b5e643f
to
f8bed4a
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.
Looks good
Signed-off-by: Tommy Carpenter <[email protected]>
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.
Minor tweak to names to match the existing convention in the repo requested but otherwise looks good. Thanks for the PR!
Signed-off-by: Tommy Carpenter <[email protected]>
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.
🎉 Thanks for the contribution
This adds the optional ability to turn off stack traces. It preserves current behavior of including them.
This option is available to users that are instantiating a logger themselves, but its not currently exposed to users of InitLoggerX
An alternative would have been to not do
lgrCfg := zap.NewProductionConfig()
inside the function and instead take a zap config, but thats not the way the original code was written.