Fix LogError argument order in WebAssemblyErrorBoundaryLogger #39223
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
added
area-blazor
pranavkm
approved these changes
Dec 29, 2021
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
Looks like @pranavkm fixed the issue https://github.com/dotnet/aspnetcore/pull/39246/files. Will need to re-run CI after that is merged. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #39202 the arguments which got passed into
LogErrorwere in the wrong order. Theexceptioncomes before themessage. It worked because thestring, Object[]overload was used instead.