Skip to content
This repository has been archived by the owner on May 23, 2024. It is now read-only.

Fix zap logger Infof #100

Merged
merged 2 commits into from
Feb 24, 2017
Merged

Fix zap logger Infof #100

merged 2 commits into from
Feb 24, 2017

Conversation

black-adder
Copy link
Contributor

No description provided.

@coveralls
Copy link

coveralls commented Feb 22, 2017

Coverage Status

Coverage remained the same at 81.989% when pulling eeaba80 on im_bad into 8630b10 on master.

@@ -41,5 +41,5 @@ func (l *Logger) Error(msg string) {

// Infof logs a message at info priority
func (l *Logger) Infof(msg string, args ...interface{}) {
l.logger.Infof(msg, args)
l.logger.Infof(msg, args...)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this indicates that you don't have correct unit tests for this

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

kinda hard to testing logging without some kind of local backend which zap doesn't provide. I can write one and plug it into zap but seems a bit overkill

@yurishkuro
Copy link
Member

@coveralls
Copy link

Coverage Status

Coverage remained the same at 81.996% when pulling 9813de0 on im_bad into 386984c on master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 81.996% when pulling 9813de0 on im_bad into 386984c on master.

@black-adder black-adder merged commit d25ce14 into master Feb 24, 2017
@black-adder black-adder deleted the im_bad branch February 24, 2017 03:02
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants