-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Improve LoggerFactory and Logger debugging #88313
Improve LoggerFactory and Logger debugging #88313
Conversation
Tagging subscribers to this area: @dotnet/area-extensions-logging |
@@ -19,7 +19,7 @@ public MessageLogger(ILogger logger, string? category, string? providerTypeFullN | |||
|
|||
public ILogger Logger { get; } | |||
|
|||
public string? Category { get; } |
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.
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.
Nullable analysis says it can't. I changed it because I didn't see any code paths that allowed null.
LoggerFactory
The changes to
LoggerFactory
make it easy to discover the common configuration for logging:Before
After
Logger
Logger
changes denormalize information back to an understandable form. It's now easy to see what providers are enabled for this logger and the min log level for each provider.Before
After