-
Notifications
You must be signed in to change notification settings - Fork 246
Conversation
@muratg - do we want to have someone take a look at this? |
@ChrisSimmons thanks for the PR! @pakrym could you review when you have some time? |
@@ -38,10 +38,15 @@ public void MessageOnly_LogsCorrectValues() | |||
logger.LogError(_state); | |||
logger.LogCritical(_state); | |||
logger.LogDebug(_state); | |||
logger.Log(LogLevel.Trace, _state); |
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.
Add a separate test method that calls new overloads (with exception and non zero event id)
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.
Sorry for the delay. I'll get to this now.
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.
Please add tests for new overloads, otherwise LGTM. |
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.
^
Wire existing Log() extension with log level to use new method. Wire up level-specific extensions to use new method Rely on null argument check in new method Add overloads without EventId and exception, patterns that were already present in the level-specific methods. Hook level-specific into these new overloads. Adds to aspnet/Logging#629 and #649
Also, is there any value to using a |
Totally, bring the Theories in. |
OK, all set. Let me know if you have any more requested changes. |
This PR expands on #629. Changes:
EventId
and anException
LogDebug()
andLogWarning()
) to use this new methodlogger
argument exception