-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
entry: break out time, level and message from data #48
Conversation
@aybabtme oops. Working on some tests. |
@@ -8,9 +8,24 @@ import ( | |||
"time" | |||
) | |||
|
|||
// An entry is the final or intermediate Logrus logging entry. It containts all |
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.
The comment should start withEntry ...
Golint
As discussed, golint in another PR.
Since the fix is implemented in the formatters, what will happen if a user takes a third party formatter? |
I think this is a formatter concern, not a concern of Logrus core. You should be able to override this functionality in your own formatters. |
Level Level | ||
|
||
// Message passed to Debug, Info, Warn, Error, Fatal or Panic | ||
Message string | ||
} |
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.
Putting them as fields of Entry
is 👍
entry: break out time, level and message from data
Replaces #33 and fixes #44.
Please review @aybatme