QuickGrid throws InvokeAsync exception when RefreshDataAsync() is called

[ViRuSTriNiTy]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Hi there,

as the title already states, QuickGrid possibly throws an InvokeAsync exception when RefreshDataAsync() is invoked from a callback associated with a background service, like a timer.

This is caused by a call to StateHasChanged() within RefreshDataAsync() without wrapping it in InvokeAsync as described in https://learn.microsoft.com/en-us/aspnet/core/blazor/components/synchronization-context?view=aspnetcore-8.0#invoke-component-methods-externally-to-update-state.

My current solution is to catch the exception and call StateHasChanged() with InvokeAsync otherwise rethrow:

try
{
    await Grid.RefreshDataAsync();
}
catch (InvalidOperationException ex)
{
    if (ex.Message.Contains("InvokeAsync", StringComparison.Ordinal))
        await InvokeAsync(StateHasChanged);
    else
        throw;
}

Expected Behavior

It would be nice to have await InvokeAsync(StateHasChanged) calls in QuickGrid to avoid the need to use try catches here and there.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

No response

Anything else?

No response

[javiercn]

@ViRuSTriNiTy thanks for contacting us.

It's not clear what you are asking. Are you suggesting that RefreshDataAsync internally dispatches the call via InvokeAsync?

[ViRuSTriNiTy]

@ViRuSTriNiTy thanks for contacting us.

It's not clear what you are asking. Are you suggesting that RefreshDataAsync internally dispatches the call via InvokeAsync?

Exactly, see section Expected behavior:

It would be nice to have await InvokeAsync(StateHasChanged) calls in QuickGrid to avoid the need to use try catches here and there.