Skip to content

feat(MultiSelect): add IsVirtualize parameter #5645

@EliasIsmail

Description

@EliasIsmail

Is there an existing issue for this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

I was wondering if it would be possible to add Pagination built in to the MultiSelect component.

I have a case in which a Collection of generic/custom objects is shown in the MultiSelect - sometimes, the number of objects is 20.000+. This leads to (maybe as expected) quite sluggish behaviour, when the component is rendered, and especially if you use the "Select all" button for example.

Currently, I have bypassed this by adding a component to the ButtonTemplate child component of the MultiSelect. The Items parameter of the MultiSelect is then bound to a list of objects, that gets updated when the user changes the page (i.e. Skip(pages).Take(pageSize)). This works somewhat, but it can be very tricky to implement and maintain, especially when you factor in the search functionality (which is awesome btw) that the MultiSelect also supports:

<MultiSelect Items="ListUpdatedByPage ... etc"

<ButtonTemplate>
    <Pagination OnPageLinkClick="OnMultiSelectPageLinkClick" PageIndex="GetMultiSelectPageIndex()" PageCount="@GetMultiSelectPageCount()"></Pagination>
 </ButtonTemplate>

</MultiSelect>

So therefore I was wondering, if Pagination in the MultiSelect was ever on the road map? I see that the Table component has it built-in, and this is the exact functionality that would be awesome for MultiSelects with large amount of data.

Kind regards

Describe the solution you'd like

Pagination parameters to the MultiSelect, like what is available in the Table component currently. Alternatively, any kind of Virtualization.

Additional context

No response

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions