Skip to content

Guidance for error handling in Blazor #11794

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

Closed
SteveSandersonMS opened this issue Jul 2, 2019 · 1 comment
Closed

Guidance for error handling in Blazor #11794

SteveSandersonMS opened this issue Jul 2, 2019 · 1 comment
Assignees
Labels
area-blazor Includes: Blazor, Razor Components Done This issue has been fixed

Comments

@SteveSandersonMS
Copy link
Member

This is part of #10472

Enumerate all the places we'd expect a developer to write some manual error handling code so we can document and explain them.

With respect to the different boundaries between framework and application code (lifecycle
methods, event handlers, dispose, DI services, rendering, etc.), which of them will terminate the circuit if there's an exception? Which of them will surface the error in a way that naturally appears to the user and/or gets logged?

The overall outcome here should be some info that can be the basis for documentation. And if necessary, tweak product code to improve anything that seems wrong about the built-in behavior.

@SteveSandersonMS
Copy link
Member Author

OK, the draft content and doc proposal is now done at dotnet/AspNetCore.Docs#13288. Since this has now become a docs issue, I'll close this as done here.

@SteveSandersonMS SteveSandersonMS added Done This issue has been fixed and removed Docs This issue tracks updating documentation labels Jul 15, 2019
@ghost ghost locked as resolved and limited conversation to collaborators Dec 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components Done This issue has been fixed
Projects
None yet
Development

No branches or pull requests

2 participants