feat: set Items as optional in ItemsProvider about fluentui-blazor HOT 12 CLOSED

No, we are not going to change that logic. Even if the result is that no rows are being returned, the grid is then no longer in a Loading state. It is not on us to interpretate if that is a satisfactory result or not.

from fluentui-blazor.

Do you have any other idea to bypass the problem with req.Count as null?

from fluentui-blazor.

I think that is something that needs to be handled on 'your' side. We can't determine what is right or wrong when null is returned.

from fluentui-blazor.

Perhaps there was a small misunderstanding.
I would like to deal with invalid input parameters on "my side" (e.g. req.Count is null) but I can't as after every ItemsProvider call the loading indicator disappears and doesn't open when ItemsProvider called again.

private GridItemsProvider<RowDto> InitialProvider => async req =>
{
    try
    {
        _grid.SetLoadingState(true);
        if (req.Count is null) throw new OperationCanceledException();
        var results = await new GridCommand(args).Execute(req.CancellationToken);
        return GridItemsProviderResult.From(
            items: results.Items,
            totalItemCount: results.TotalItemCount
        );
    }
    catch (OperationCanceledException ex) {}

    return GridItemsProviderResult.From(
        items: Array.Empty<RowDto>(),
        totalItemCount: -1
    );
};

from fluentui-blazor.

The disappearing of the loading indicator is by design. The provider has retuned, so loading is done.

from fluentui-blazor.

So in the case of using the Virtualize parameter, which gives req.Count as null on the first load? Should I use an external loading indicator?

from fluentui-blazor.

No, you should anticipate on that first request returning null. You know that will always be the case.

from fluentui-blazor.

At this moment, I have no way to handle it.
I tried with OnAfterRender, loading flags, etc., but nothing worked.

from fluentui-blazor.

Sorry to hear that. Up until now, there has been no issues/discussions around this. You must have a pretty unique use case.

from fluentui-blazor.

I will make a reproduced example and report the bug issue if it is not a problem.

from fluentui-blazor.

Sure, no problem. But as this is one of the most used (and most complex) components, we will be very careful to not have any breaking changes. So no guarantee that your issue can or will be resolved.

And please create a new issue so we don't have all the bagage from the discussions in this one :)

from fluentui-blazor.

Of course!

from fluentui-blazor.