Skip to content

fix: consolidate duplicate TransactionPagination into single correct implementation#230

Merged
portableDD merged 1 commit into
Nexacore-Org:mainfrom
Hollujay:fix/154-transaction-pagination
Jun 25, 2026
Merged

fix: consolidate duplicate TransactionPagination into single correct implementation#230
portableDD merged 1 commit into
Nexacore-Org:mainfrom
Hollujay:fix/154-transaction-pagination

Conversation

@Hollujay

Copy link
Copy Markdown
Contributor

Description

📝 Context

The previous transaction pagination component had a hardcoded layout ( 1, 2, 3, 4, 5 ... ) and lacked proper
state-driven navigation for large datasets. This made it difficult for users to navigate effectively when they
have many pages of transactions.

🚀 What changed

This PR updates the TransactionPagination component to introduce dynamic ellipsis-based pagination, along with
UI enhancements:

• Dynamic Page Calculation: Implemented getVisiblePages() to dynamically calculate and render page numbers with
ellipses ( ... ) based on the current page and total pages (e.g., 1 ... 4 5 6 7 8 ... 12 ).
• Icon Updates: Replaced text-based "Previous" and "Next" buttons with ChevronLeft and ChevronRight icons
from lucide-react for a cleaner, modern look.
• Improved Styling:
• Updated buttons with proper active, hover, and disabled states (e.g., cursor not-allowed when on the first
or last page).
• Aligned the layout so that "Showing {start} to {end} of {total} results" sits nicely on the left (or on top
for mobile screens), and the pagination controls sit on the right.
• Refined the active state to use the primary theme color.

📸 Screenshots

Screenshot from 2026-06-24 16-35-13

🧪 How to test

  1. Navigate to the transactions page with a dataset large enough to trigger multiple pages (e.g., 100+ items).
  2. Verify the text on the left updates correctly (e.g., "Showing 51 to 60 of 120 results").
  3. Click through the pages and ensure the ellipsis ( ... ) shifts correctly as you move towards the middle and
    end of the list.
  4. Verify the Previous and Next arrows disable appropriately on the first and last pages.

Closes #154

@vercel

vercel Bot commented Jun 24, 2026

Copy link
Copy Markdown

@Hollujay is attempting to deploy a commit to the Emmanuel Dorcas' projects Team on Vercel.

A member of the Team first needs to authorize it.

@drips-wave

drips-wave Bot commented Jun 24, 2026

Copy link
Copy Markdown

@Hollujay Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@portableDD portableDD left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@portableDD portableDD merged commit 56c9d80 into Nexacore-Org:main Jun 25, 2026
1 of 2 checks passed
Olasunkanmi975 pushed a commit to Olasunkanmi975/NexaFx-web that referenced this pull request Jun 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove duplicate TransactionPagination component and consolidate into one correct implementation

2 participants