feat(paginator): add initialPage prop for page initialization

[j0rgedev]

Defect Fixes

#7023

Resolution

Cause

The Paginator component did not have a way to initialize on a specific page.

Solution

Added a new initialPage prop to allow users to specify the page to initialize the Paginator.

Additional Notes

• Added tests to cover the new initialPage functionality.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Skipped Deployments

Name	Status	Preview	Updated (UTC)
primevue	⬜️ Ignored (Inspect)	Visit Preview	Jan 13, 2025 1:22am
primevue-v3	⬜️ Ignored (Inspect)	Visit Preview	Jan 13, 2025 1:22am

[tugcekucukoglu]

What about first property? What is the difference between initialPage and first?

[j0rgedev]

Hello @tugcekucukoglu, I just reviewed this in more detail, and it seems that first has a slightly different purpose. While it’s true that if you set :first="11" (with 10 rows per page), it automatically moves to the second page, the first prop also works in cases like :first="2", where it only shows rows starting from the third one (skipping the first two). This aligns with its description: "Zero-relative number of the first row to be displayed."

On the other hand, the new initialPage prop I introduced is specifically designed to set the initial page of the paginator without affecting the rows or their offsets. It’s a more targeted way of initializing the paginator to a specific page.

So, while both props may overlap in functionality, their use cases are different. I believe this justifies the new prop, but I’d be happy to hear your feedback if you think it’s unnecessary or could be improved.