-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Update ILogger
documentation to clarify formatter behavior when using extension methods
#10345
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
Conversation
…ng extension methods
Tagging subscribers to this area: @dotnet/area-extensions-logging |
Learn Build status updates of commit dd3cbfb: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Learn Build status updates of commit 21a34ed: ❌ Validation status: errorsPlease follow instructions here which may help to resolve issue.
xml/Microsoft.Extensions.Logging/ILogger.xml
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. For any questions, please:
|
Learn Build status updates of commit f490ee1: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Summary
As described in the issue, the
ILogger
extension methods defined inLoggerExtensions
pass in a formatter that ignores theexception
parameter passed in. This is being made clear so that developers do not assume otherwise.Fixes #10318