Implement Pagination for API Keys Table

unrenamed commented 1 month ago

Preliminary Checks

[X] I have reviewed https://unkey.com/docs for existing features that would solve my problem
[X] I have searched for existing feature requests: https://github.com/unkeyed/unkey/issues
[X] This issue is not a question, general help request, or anything other than a feature request directly related to Unkey. Please ask questions in our Discord community: https://unkey.com/discord.

Is your feature request related to a problem? Please describe.

Yes, the feature request is related to a significant usability problem. Currently, the API Keys table displays only the first page of results, limiting users' ability to access or view the remaining 400 keys from a sample of 500. This can lead to frustration and inefficiencies when users need to manage, review, or analyze a larger set of keys, as they cannot navigate beyond the initial page.

Describe the solution

The proposed solution is to implement a pagination feature for the API Keys table. This would involve one of the following approaches:

Pagination Controls Adding controls (such as "Previous," "Next," and page numbers) to navigate through the different pages of keys.
Dynamic Loading Allowing the table to load a specific number of keys per page (e.g., 10, 20, or 50), providing a manageable view of the data. Given the existing cursor-based pagination in the API, this may be the most optimal approach.

Describe alternatives you have considered (if any)

Alternatives considered include:

Infinite Scrolling: Automatically load more keys as users scroll. This could complicate navigation.
Search and Filter Options: Enhance search functionalities to find specific keys quickly, but this doesn't resolve the viewing issue.