From c5fa5d05d6bb9460644eb00ab391cad8ad72d11a Mon Sep 17 00:00:00 2001
From: campersau <buchholz.bastian@googlemail.com>
Date: Wed, 29 Dec 2021 15:07:52 +0100
Subject: [PATCH] Fix LogError argument order in WebAssemblyErrorBoundaryLogger

---
 .../src/Services/WebAssemblyErrorBoundaryLogger.cs            | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/Components/WebAssembly/WebAssembly/src/Services/WebAssemblyErrorBoundaryLogger.cs b/src/Components/WebAssembly/WebAssembly/src/Services/WebAssemblyErrorBoundaryLogger.cs
index 97db51b9fe09..62090936712d 100644
--- a/src/Components/WebAssembly/WebAssembly/src/Services/WebAssemblyErrorBoundaryLogger.cs
+++ b/src/Components/WebAssembly/WebAssembly/src/Services/WebAssemblyErrorBoundaryLogger.cs
@@ -12,14 +12,14 @@ internal sealed class WebAssemblyErrorBoundaryLogger : IErrorBoundaryLogger
 
     public WebAssemblyErrorBoundaryLogger(ILogger<ErrorBoundary> errorBoundaryLogger)
     {
-        _errorBoundaryLogger = errorBoundaryLogger ?? throw new ArgumentNullException(nameof(errorBoundaryLogger)); ;
+        _errorBoundaryLogger = errorBoundaryLogger ?? throw new ArgumentNullException(nameof(errorBoundaryLogger));
     }
 
     public ValueTask LogErrorAsync(Exception exception)
     {
         // For, client-side code, all internal state is visible to the end user. We can just
         // log directly to the console.
-        _errorBoundaryLogger.LogError(exception.ToString(), exception);
+        _errorBoundaryLogger.LogError(exception, exception.ToString());
         return ValueTask.CompletedTask;
     }
 }