Skip to content

Include the exception when logging in WebAssemblyErrorBoundaryLogger #39202

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

Merged
merged 1 commit into from
Dec 27, 2021

Conversation

pranavkm
Copy link
Contributor

Fixes #39039

@pranavkm pranavkm requested a review from a team as a code owner December 27, 2021 18:48
@ghost ghost added the area-blazor Includes: Blazor, Razor Components label Dec 27, 2021
@pranavkm pranavkm enabled auto-merge (squash) December 27, 2021 19:02
@pranavkm pranavkm merged commit a8e0bed into dotnet:main Dec 27, 2021
@ghost ghost added this to the 7.0-preview1 milestone Dec 27, 2021
@@ -21,7 +19,7 @@ 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());
_errorBoundaryLogger.LogError(exception.ToString(), exception);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is wrong, as the exception comes before the message. See #39223

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-blazor Includes: Blazor, Razor Components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Using Custom ILogger with ErrorBoundary produces exception = null
3 participants