-
Notifications
You must be signed in to change notification settings - Fork 10
Improve logging on Completer #285
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
Not sure if exposing a Log method is the best way to go, but wanted to respect the debug configuration.
The idea is to make it more explicit that on error situations the offset returned is zero. The function was doing that but in a way that we had to check if the offset var was not being assigned to some value, in the end it never is, it is always 0 (or I got something wrong).
The var was never initialized, maybe it could be some sort of empty/default thing, but the name was at least misleading. Since the function returns a slice just using nil for empty slice is idiomatic in Go and should work.
Codecov Report
@@ Coverage Diff @@
## master #285 +/- ##
==========================================
- Coverage 42.32% 41.75% -0.57%
==========================================
Files 52 52
Lines 7318 6378 -940
==========================================
- Hits 3097 2663 -434
+ Misses 3931 3429 -502
+ Partials 290 286 -4
Continue to review full report at Codecov.
|
vitorarins
left a comment
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.
💯
|
wow this is old, sorry =( |
|
fala xiru véio!
Best Regards,
Alfredo Tomio Junior
+31 684431787
…On Fri, Jan 13, 2023 at 1:30 AM Tiago Cesar Katcipis < ***@***.***> wrote:
Merged #285 <#285> into master.
—
Reply to this email directly, view it on GitHub
<#285 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGWUICAORDDFAUOBE7FVHLWSCO37ANCNFSM4TQ2V3MA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Not sure if exposing a Log method is the best way to go, but wanted to respect the debug configuration.