Peter Morris
Peter Morris
Records are in the next preview, so let's look at it then :)
It's tricky in validation because none of the Blazor EditContext stuff is async, which is partly why I haven't started to tackle this yet.
Your action subscriber code should be synchronous. If you do any asynchronous work here then it's up to you to deal with problems :) My advice would be to InvokeAsync...
You don't have to await it. You just using InvokeAsync to ensure it is thread-safe _ = InvokeAsync(async() => { await DoWhatever(); StateHasChanged(); });
This is a fault with Blazor. I registered it, but a bot closed it https://github.com/dotnet/aspnetcore/issues/19271
Looks like the desired Blazor behaviour. I'd welcome a PR if you'd like to submit one ;)
Do you have any suggestions for how to implement that?
I can't tie it into a specific asp.net environment because it might be running in a console app, MAUI app, or even WinForms.
I'm not sure about this. If I disable it then you'll get unpredictable errors / memory leaks that are difficult to track down over time. If I leave it in...
My guess is that you are dispatching actions from App.razor before the app has even rendered, is that correct? If not, I'll definitely need more info than "broken everywhere" or...