Artyom M.
Artyom M.
Hi! > I haven't been able to find these changes in v6.3.1 Since this pull request has not been merged, the changes are not included in any version of the...
https://github.com/MudBlazor/MudBlazor/discussions/6880#discussioncomment-5940762
> We followed the advice documented in the code itself and error message by setting the PopoverOptions.ThrowOnDuplicateProvider to false during configuration in Program.cs however this seems to have had no...
Hi. This is one of the significant issues in MudBlazor. I have addressed some occurrences of `async void` and I am gradually rewriting services to utilize `Task` support, as many...
> This problem apparently is still around in 6.0.15. Although I don't get any error messages along the lines of "Event # is already tracked", no dialog was showing for...
Closing as duplicate of https://github.com/MudBlazor/MudBlazor/issues/4720
The #4895 is merged. This can be merged and then for .net 7 as breaking change we can remove the non async api and the component will work as intended.
The problem is, that the unit test behaves differently compared to real world in some scenario. In unit test the old non async methods will have `Dialog` not empty, while...
Ok, will do then