зеркало из https://github.com/dotnet/aspnetcore.git
Fix LogError argument order in WebAssemblyErrorBoundaryLogger (#39223)
This commit is contained in:
Родитель
de86e242aa
Коммит
2a2f285430
|
@ -12,14 +12,14 @@ internal sealed class WebAssemblyErrorBoundaryLogger : IErrorBoundaryLogger
|
||||||
|
|
||||||
public WebAssemblyErrorBoundaryLogger(ILogger<ErrorBoundary> errorBoundaryLogger)
|
public WebAssemblyErrorBoundaryLogger(ILogger<ErrorBoundary> errorBoundaryLogger)
|
||||||
{
|
{
|
||||||
_errorBoundaryLogger = errorBoundaryLogger ?? throw new ArgumentNullException(nameof(errorBoundaryLogger)); ;
|
_errorBoundaryLogger = errorBoundaryLogger ?? throw new ArgumentNullException(nameof(errorBoundaryLogger));
|
||||||
}
|
}
|
||||||
|
|
||||||
public ValueTask LogErrorAsync(Exception exception)
|
public ValueTask LogErrorAsync(Exception exception)
|
||||||
{
|
{
|
||||||
// For, client-side code, all internal state is visible to the end user. We can just
|
// For, client-side code, all internal state is visible to the end user. We can just
|
||||||
// log directly to the console.
|
// log directly to the console.
|
||||||
_errorBoundaryLogger.LogError(exception.ToString(), exception);
|
_errorBoundaryLogger.LogError(exception, exception.ToString());
|
||||||
return ValueTask.CompletedTask;
|
return ValueTask.CompletedTask;
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
Загрузка…
Ссылка в новой задаче