Use Backend Pagination and Search in Management Portal API List
Open
Nobody has claimed this yet.
Area/Management
Type/UX
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Current Behavior
The Management Portal frontend currently loads all APIs at once and stores them in React context.
This approach is inefficient and causes performance issues as the API list grows.
Proposed Frontend Changes
Update API fetching logic to support pagination and search:
apiRefresh→ fetchquery=""andstart=0apiFetch→ acceptq,offset,limit(e.g.,?q=pet&offset=20&limit=20)- Clear previous API list when query parameters change to avoid stale data.
- Ensure the UI handles partial API loads gracefully (loading states, incremental list rendering).
- Search input in the frontend should trigger backend search via API rather than filtering locally.
Benefits
- Frontend performance scales with large API lists
- Smooth and responsive API list experience
- Consistency with backend pagination and search behavior
Contributor guide
No contributing guide indexed for this repository
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 frontend API fetching logic, especially apiRefresh and apiFetch, and inspect how the React context stores the API list. Verify requests use q, offset, and limit, query changes clear stale results, search reaches the backend, and partial loads show responsive incremental results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react
- Domain
- api, frontend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100