-
Notifications
You must be signed in to change notification settings - Fork 34
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
feat: implemented structured logging #54
Conversation
Codecov Report
@@ Coverage Diff @@
## main #54 +/- ##
==========================================
- Coverage 92.60% 90.85% -1.75%
==========================================
Files 5 6 +1
Lines 284 361 +77
==========================================
+ Hits 263 328 +65
- Misses 20 32 +12
Partials 1 1
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Signed-off-by: Skye Gill <[email protected]>
ad176d6
to
59cff96
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, nice work
Signed-off-by: Skye Gill <[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.
LGTM, minor suggestions.
One thing I'm wondering is how to log in hooks. It's not immediately obvious to me if that's possible.
Co-authored-by: Todd Baert <[email protected]> Signed-off-by: Skye Gill <[email protected]>
That would be something for the application author to decide, there's nothing stopping them from placing a logger inside their hook struct and using it in the callbacks. |
No description provided.