PaginationState needs to have public methods to set the object as it can then be used with custom components.

[amiddles]

main...amiddles:aspnetcore:patch-1

I simply modified the set total count method to make it public. I've no idea why it was locked down but it's a pain when you can't use a quickgrid but you do need pagination, which is already setup via the Paginator component.

This will allow for more flexibility. I've no idea how to merge the branches as I thin kit needs permission.

In my case, I have a customer table that has other special rows that don't work with a quickgrid, but I do still want o paginate it and not t have to write my own.

Please either approve and merge the fix or modify the source.

[javiercn]

@amiddles thanks for contacting us.

If we understood correctly, is it the case that you want to use the PaginationState component outside of the QuickGrid component (with your own component)?

[amiddles]

Yes, that is the correct assumption.

I have a table similar to a quick grid but where the rows are variable and might have components in them, or be a different size. The Quickgrid doesn't really accommodate this. there are also other cases where you might want pages of components but not a grid as well.

So basically being able to use the pagination components freely where I want is needed.
The methods should never have been marked internal as you just don't know who could use your component in the future.

If the concern is that someone could modify the collection and then not update their component, provide an event for that in the method that can fire and a note about how to use it.

[javiercn]

@amiddles thanks for the additional details.

Paginator is currently designed to work with QuickGrid, it might be able to be used outside of it, but we would need to do a design review to make sure that it's something we are happy with. This is not currently a priority for us, especially since this component is not complex and you can have your own copy in your project (or create a general purpose nuget package for the comunity).

For reference, the code is https://github.com/dotnet/aspnetcore/tree/main/src/Components/QuickGrid/Microsoft.AspNetCore.Components.QuickGrid/src/Pagination

[amiddles]

This isn't really a design decision for microsoft to make. what matters is how clients wan to use the tools. I just need the underlying class to be marked public so that I can use the existing component as is without having to make my own. I will if needed but that seems silly when the tool is already there. You only need to mark the method public and then it will work without affecting anyone else.

[barruka]

@javiercn I think this is really important and needed the moment we are using an external API with custom parameteres.

Example:

https://api.example.com/users?page=1&pagesize=25

returns:

SearchResponse<UserDto>
{
	TotalItems = response.TotalItems,
	Items = [.. response.Items.Select(i => i.AsDto())],
	Page = response.Page,
	PageSize = response.PageSize,
	SortBy = response.SortBy,
	SortDescending = response.SortDescending,
	Filters = response.Filters
};

So, the page has a Quickgrid:

   <QuickGrid Items="@items" Pagination="@pagination">
        <PropertyColumn Title="User name" Property="@(c => c.Name)" Sortable="true" InitialSortDirection="SortDirection.Ascending" IsDefaultSortColumn="true" />
        <PropertyColumn Title="Email" Property="@(c => c.Email)" Sortable="true" />
        <PropertyColumn Title="Status" Property="@(c => c.Status.Name)" Sortable="true" />
    </QuickGrid>

Then, fetchs the data:

@inject ApiHttpClient httpClient

@code {
   IQueryable<UserDto> items = default!;
   PaginationState pagination = new PaginationState { ItemsPerPage = AppDefaults.ItemsPerPage };

   protected override async Task OnInitializedAsync()
   {
      var url = $"/users?page={1 + pagination.CurrentPageIndex}&pagesize={pagination.ItemsPerPage}";
      var response = await httpClient.GetResponse<SearchResponse<UserDto>>(url);

      items = response?.Items?.AsQueryable() ?? new List<UserDto>().AsQueryable();
   }
}

So in the SearchResponse<UserDto> of the api, we got a TotalItems property with the total items (lets say 500,000 (5 * 10^5).
I think we need to call paginator.SetTotalItemCountAsync() with the response.TotalItems.

Either way, how can we notify the paginator that there are 500,000 items that match the request parameters?