ErrorBoundary coverage enhancements

[guardrex]

Fixes #33109

Thanks @TimMurphy! ... again! Although you hit a pain point with the explanation on wrapping the component hierarchy, I'm glad that you wrote in about this section (and the other one). This is vastly improved now, and it should clear up the confusion about about what the error boundary should wrap.

When this goes live, I'll ping you here with the link to it.

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/blazor/fundamentals/handle-errors.md	Handle errors in ASP.NET Core Blazor apps

[guardrex]

It's live⚡now ...

https://learn.microsoft.com/en-us/aspnet/core/blazor/fundamentals/handle-errors?view=aspnetcore-8.0#error-boundaries

[TimMurphy]

Thanks Luke for your quick responses. Not the answers I was hoping for but at least I know why and how to proceed.

…

On Fri, 19 Jul 2024 at 02:02, Luke Latham ***@***.***> wrote: It's live⚡now ... https://learn.microsoft.com/en-us/aspnet/core/blazor/fundamentals/handle-errors?view=aspnetcore-8.0#error-boundaries — Reply to this email directly, view it on GitHub <#33110 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADFDDSNMJYSUFFBJZ576OTZM7RITAVCNFSM6AAAAABLC4X2RCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZWHEZTMNBWGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[guardrex]

If the framework features are limiting what you'd like to do, open a new feature request with the product unit at ...

https://github.com/dotnet/aspnetcore/issues

Perhaps, they'll consider your suggestion(s). First tho, search their open issues. I'm under the impression that they already know that the global exception handling experience is a bit rough. They might already be planning something for a future release. You can also look at their closed issues for any suggestions that they decided not to pursue.

[TimMurphy]

Thanks, I'll check it out.

…

On Fri, 19 Jul 2024 at 04:39, Luke Latham ***@***.***> wrote: If the framework features are limiting what you'd like to do, open a new feature request with the product unit at ... https://github.com/dotnet/aspnetcore/issues Perhaps, they'll consider your suggestion(s). First tho, search their open issues. I'm under the impression that they already know that the global exception handling experience is a bit rough. They might already be planning something for a future release. You can also look at their closed issues for any suggestions that they decided not to pursue. — Reply to this email directly, view it on GitHub <#33110 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADFDDU43A4GO7LKZJJHGUDZNADVPAVCNFSM6AAAAABLC4X2RCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZXGI2TKNJTGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[guardrex]

Sure thing ... and I forgot to mention that you filter the blazor issues with label:area-blazor. A search like this might find some things ...

https://github.com/dotnet/aspnetcore/issues?q=is%3Aissue+label%3Aarea-blazor+exception+handling

[guardrex]

It turns things like this up, where there's a discussion that we were just having. Also, the revisions that I just put in should help devs understand and help with the confusion.

dotnet/aspnetcore#56413