stacklok / stacklok/toolhive-studio
Pagination for registry API servers
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 167
- Forks
- 24
- Avg merge
- 11h 32m
- Merged PRs (30d)
- 91
Description
The registry server API supports pagination when listing servers, which means the UI is only displaying the first 100 returned. For registries with > 100 servers, this means some are inaccessible in the UI.
I think the UI should retrieve all servers (so the search filter can apply over all of them), and implement pagination for the cards display.
Related CLI/API issue:
- stacklok/toolhive#3069
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the UI entry point that fetches and displays registry servers, then trace how the search filter and server cards consume the paginated API response. Confirm the registry API pagination shape and make the UI cover all servers for searching while paginating the card display; done means servers beyond the first 100 are searchable and viewable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100