Skip to content

Commit f490ee1

Browse files
committed
Update based on feedback
1 parent 21a34ed commit f490ee1

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

xml/Microsoft.Extensions.Logging/ILogger.xml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<Type Name="ILogger" FullName="Microsoft.Extensions.Logging.ILogger">
1+
<Type Name="ILogger" FullName="Microsoft.Extensions.Logging.ILogger">
22
<TypeSignature Language="C#" Value="public interface ILogger" />
33
<TypeSignature Language="ILAsm" Value=".class public interface auto ansi abstract beforefieldinit ILogger" />
44
<TypeSignature Language="DocId" Value="T:Microsoft.Extensions.Logging.ILogger" />
@@ -143,7 +143,7 @@
143143
<param name="exception">The exception related to this entry.</param>
144144
<param name="formatter">Function to create a <see cref="T:System.String" /> message of the <paramref name="state" /> and <paramref name="exception" />.</param>
145145
<summary>Writes a log entry.</summary>
146-
<remarks>Note: When using extension methods such as <see cref="M:Microsoft.Extensions.Logging.LoggerExtensions.Log(Microsoft.Extensions.Logging.ILogger,Microsoft.Extensions.Logging.LogLevel,Microsoft.Extensions.Logging.EventId,System.Exception,System.String,System.Object[])"/> and <see cref="M:Microsoft.Extensions.Logging.LoggerExtensions.LogError(Microsoft.Extensions.Logging.ILogger,System.Exception,System.String,System.Object[])"/>, the <paramref name "formatter"> provided to this method will not add the <paramref name="exception"/> to the log message. When using these extension methods, implementations should explicitly append the <paramref name="exception"/> to the log message.</remarks>
146+
<remarks>The default <paramref name="formatter" /> provided by the logger extension methods doesn't include the <paramref name="exception" /> when formatting messages. It's essential for implementations of this method to decide how exceptions should be incorporated into the logs.</remarks>
147147
</Docs>
148148
</Member>
149149
</Members>

0 commit comments

Comments
 (0)