-
Notifications
You must be signed in to change notification settings - Fork 53
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
refactor: Purge all println and ban it #253
Conversation
Here they are actually hidding what is actually untested
Instead of println
Codecov Report
@@ Coverage Diff @@
## develop #253 +/- ##
===========================================
- Coverage 58.57% 58.49% -0.09%
===========================================
Files 103 103
Lines 9846 9834 -12
===========================================
- Hits 5767 5752 -15
- Misses 3449 3454 +5
+ Partials 630 628 -2
|
This makes the benchmarks output a lot of logs if |
It does? Cheers for checking - will have a look - thought that would be the same as before (maybe it is lol?) |
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
Is doing in dev branch - will merge this after creating a new ticket to fix the bench spam: |
* Use logger in bench package * Log command result instead of println * Remove printlns from db_test Here they are actually hidding what is actually untested * Write to log in db.printstore Instead of println * Use logger in db.tests * Delete println * Ban fmt.PrintX
Closes #242
Commits are pretty broken down - more involved/controversial changes should have there own commit, with
Delete println
containing the benign.Please speak out if you have concerns, this is very much a proposal (with my vote for it atm). Not a problem if this is rejected.