feat: add configurable rows-per-page selector #58
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
This PR enhances the table pagination experience by allowing users to choose how many rows to display per page, instead of the previous fixed 10 rows. While the default remains 10 rows for consistency, users can now select 20, 50, 100, or “All” to view more results at once.
The update also improves navigation by:
Changes:
pageSelect) in favor of a Rows per page selector (pageSizeSelect).computeTotalPages()to handle dynamic page size changes and ensure valid navigation boundaries.renderShowingText()to show the visible range and total offers.updatePrevNextDisabledState()to handle disabling navigation buttons when appropriate.Pre-commit Checks:
pre-commit run --all-fileslocally with no issues found.UI Design and Aesthetics:
Screenshots:
