OWASP / OWASP/Nest

Standardize pagination component for consistency and reusability

Open
#3,448 3 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
451
Forks
702
Avg merge
22h 59m
Merged PRs (30d)
91

Description

**Is your feature request related to a problem? Please describe.**
We currently have two different pagination implementations in the frontend, which leads to inconsistent UI/UX across the application.
- Most pages use a custom pagination component located at `frontend/src/components/pagination`, which looks consistent and matches our design system.
- However, `projects/dashboard/metrics` uses `Pagination` from `@heroui/react`, and its appearance and behavior do not align with the rest of the app.

**Describe the solution you'd like**
I’d like to standardize pagination across the application by reusing our existing custom pagination component everywhere, including `projects/dashboard/metrics`.
- Clear, minimal props (currentPage, totalPages, onPageChange)
- Centralized styling and behavior
- Easy customization without duplicating logic

**Are you going to work on implementing this?**

- [x] Yes
- [ ] No

### Pagination Component:
Image

### @heroui/react:
Image

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.