-
Notifications
You must be signed in to change notification settings - Fork 72
Conversation
5f168e3
to
966afe7
Compare
{ | ||
if (_logger.IsEnabled(LogLevel.Verbose)) | ||
{ | ||
_logger.LogVerbose(LoggingEventIds.MethodMismatch, $"{context.Request.Method} requests are not supported"); |
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.
Debug
Take a look at aspnet/Mvc@da731fc - there's a super efficient and more slightly more cleanly pattern added recently |
Updated |
static LoggerExtensions() | ||
{ | ||
_logMethodNotSupported = LoggerMessage.Define<string>( | ||
logLevel: LogLevel.Debug, |
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.
I talked to Ryan and he said that most of these should be Verbose, so you always end up with at least one verbose message when the middleware does not handle a request. If it does handle the request then there should be one or more Informational messages.
Updated |
eventId: 5, | ||
formatString: "The request path {Path} does not match an existing file"); | ||
_logPathNotModified = LoggerMessage.Define<string>( | ||
logLevel: LogLevel.Verbose, |
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.
Info
Updated again |
|
8979a95
to
37f19b4
Compare
Fixes #69
please review @Tratcher @rynowak