TagHelper for Pager does not allow "All"

[Kyle]

It appears that using the Razor syntax allows us to set:

new object[] { 5, 10, 20, 50, "All" }

However, the TagHelper does not. It only supports ints. Therefore, I do not have a way to use the special "all" keyword for the pager while using TagHelpers.

[Alexander]

Hi Kyle,

Thank you for reaching out.

Indeed, your supposition is precisely accurate. At this stage, the page-sizes TagHelper attribute exposes only an integer array overload which can be incorporated. However, this is a valid request as users may have the need to display all the data from the PageSizes DropDownList for a TagHelper scenario in particular.

Thus, I have logged the following items where you can track the items' status. Both are symbiotically connected. Hence, you can review either of the items which you find more intuitive:

• Feedback portal item: https://feedback.telerik.com/aspnet-core-ui/1627319-grid-pagesizes-taghelper-attribute-does-not-expose-an-ienumerable-overload

• GitHub item: https://github.com/telerik/kendo-ui-core/issues/7556

I understand the importance this may have for you and in this regard, I have provided an enhancement candidate that is pending further evaluation from our respective developer subject matter experts and quality assurance engineers.

For the time being, I would recommend adding the "All" option programmatically by utilizing the native widget Grid counterpart's .setOptions() method:

<script type="text/javascript">
        $(document).ready(function () {
            $("#grid").data("kendoGrid").setOptions({
                pageable: {
                    pageSizes: [5, 10, "All"]
                }
            })
        })
</script>

This should then produce the following visual representation upon interacting with the page sizes:

For further bringing this to our attention, I have also updated your  Telerik points as a token of appreciation.

Kind Regards,
Alexander
Progress Telerik

[Alexander]

Hi Kyle,

I'm happy to let you know that I have received the green light for the provided changes and that the fix will be available within our next available release. I again would like to thank you for your contribution. It was invaluable to me in order to unravel the fixed candidate.

[Kyle]

Alexander,

Thank you for your prompt attention and quick turn around.

While we switched over to using the Razor syntax due to other reasons, I am constantly pleased to see Progress Telerik respond so quickly to our needs.

Keep up the great work!
Kyle