Pagination Bug Fixes
paginationServeris a new property that allows pagination to work correctly when using server-side pagination. Use it when you are paging data from a server only. It was always assumed that the data needed to be sliced, instead, this now only happens for client-side pagination where the total records are typically in the data set.
Make sure that when using server-side pagination that you always use the paginationTotalRows property. Your target REST API should return a total record count (not the count of records on a page call) either in the response or the header.
- Switching the rows per page when on the last row and using client-side paging will now correctly navigate to the recalculated last page instead of page 1
- when using
paginationServerpage navigation this behavior will be bypassed
Documentation
- added server-side pagination storybook