-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
MudBlazor template is missing unhandled exceptions div #9020
Comments
Hello, Could this "help" ? To summarize, it's mainly because the Task is not (may not be) awaited. Which is potentially understandable if the original method was not a task : the calls to it were not "awaited". So I would not qualify this as a bug but rather as a bad programming practice (no offence to you, of course). Regards, |
Yes i known all that An unhandled error has occurred. Reload 🗙
this is as expected - do You think it should not be there anymore? |
To be honest, as I feel it's a "bad programming practice", I would not even try to solve this. It would add mess where there's already enough, I think. Don't get me wrong, though, I understand your need to handle such exception in a task. But, as many sources seem to agree, the correct way to handle it properly is to await the call. Period. Regards, |
so You guys think that default blazor option for handling unhandled exceptions - 'Down bar showing that some error occured and You can try reload' |
I think you guys are discussing two different things. The issue was also brought up on the template repo MudBlazor/Templates#451 |
exacly - it is just example nothing more. |
Hi everyone, as part of upgrading templates for the upcoming MudBlazor 7.0.0 release, I rebuilt templates from scratch and the error |
Bug type
Component, Other
Component name
MainLayout
What happened?
in default MudBlazor serwerside template
in routes.razor / old index.html
You guys are missing
<div id="blazor-error-ui"> <span style="color:black">An unhandled error has occurred.</span> <a href="" class="reload">Reload</a> <a class="dismiss">🗙</a> </div>
without this when there is an unhandled expeption
for example
if in famus 'counter' component page we change from
to
then onclick there is no exception throwed in VS
and app just freeze.
BE AWARE
IN TRY MUDBLAZOR LINK everything is ok
in default New Project / MudBlazor template NO.
Expected behavior
in defualt template error handling 'down bar' should be also implemented
Reproduction link
https://try.mudblazor.com/snippet/mEGIaTGkGgKtdJXD
https://stackoverflow.com/questions/78493661/blazor-serverside-why-is-exception-not-thrown-when-in-task-how-to-avoid-this
Reproduction steps
...
Relevant log output
No response
Version (bug)
6.19
Version (working)
No response
What browsers are you seeing the problem on?
Chrome
On which operating systems are you experiencing the issue?
Windows
Pull Request
Code of Conduct
The text was updated successfully, but these errors were encountered: