-
Notifications
You must be signed in to change notification settings - Fork 272
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
Avoid introducing go-vet noise #30
Conversation
Ack, sorry tests fail. will fix-- second |
Currently, go-logging introduces go-vet noise into client codebases. - introduces `-f` variants - changes old, non `-f` variants to use fmt.Sprint, as the `(*Logger) Panic` and `(*Logger) Fatal` functions do. - Adds a few comments that help logger.go pass golint - Fixes op#29
|
until op/go-logging#30 is merged
until op/go-logging#30 is merged
I can't merge this change as it would break backwards compatibility. I believe the API is sane though. Would be great if there were a generic log interface somewhere following this API, with an implementation for this and many other logging libraries. |
If you won't merge, why is this still open? |
I did listen to the community and merged #12 which added this functionality. Thanks. |
until op/go-logging#30 is merged
until op/go-logging#30 is merged This commit was moved from ipfs/go-unixfs@8e3a210
Fixes #29