Is your feature request related to a problem? Please describe.
The Database page already supports pagination, but the Auth page currently displays only the first 100 users. As a result, users beyond this limit cannot be viewed or accessed from the Auth page, creating an inconsistent experience compared to the Database page.
Describe the solution you'd like
Add pagination support to the Auth page user list, similar to the existing implementation on the Database page. This would allow users to navigate through all available user records instead of being restricted to the first 100 entries.
Describe alternatives you've considered
One alternative would be increasing the number of users returned in a single request. However, implementing pagination would be more scalable, performant, and consistent with the behavior already present on the Database page.
Additional context
This issue was suggested by a maintainer:
We have pagination on database page.
But on auth page, it only shows the first 100 users and limits access to the next users.
So we can add pagination to the auth page as well.
Proposed Approach
- Inspect the current Auth page implementation and data-fetching logic.
- Verify whether backend pagination support already exists for the relevant endpoint.
- Reuse the existing pagination pattern from the Database page where applicable.
- Implement pagination controls on the Auth page.
- Test navigation across multiple pages and validate behavior with larger datasets.
ETA
Tomorrow morning.
Suggested Labels
- gssoc:approved
- type:feature
- level:beginner
Is your feature request related to a problem? Please describe.
The Database page already supports pagination, but the Auth page currently displays only the first 100 users. As a result, users beyond this limit cannot be viewed or accessed from the Auth page, creating an inconsistent experience compared to the Database page.
Describe the solution you'd like
Add pagination support to the Auth page user list, similar to the existing implementation on the Database page. This would allow users to navigate through all available user records instead of being restricted to the first 100 entries.
Describe alternatives you've considered
One alternative would be increasing the number of users returned in a single request. However, implementing pagination would be more scalable, performant, and consistent with the behavior already present on the Database page.
Additional context
This issue was suggested by a maintainer:
Proposed Approach
ETA
Tomorrow morning.
Suggested Labels