elastic / elastic/package-registry
Support pagination on responses
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 52
- Forks
- 81
- Avg merge
- 9h 53m
- Merged PRs (30d)
- 52
Description
Responses to some endpoints can be quite big and are only going to grow when all packages are requested, specially for /search. Some clients don't benefit of having the whole response at a time, as they may need to paginate too for UX reasons.
Add support for pagination of responses, at least for the /search endpoint.
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 /search endpoint and its response contract in the Go service. Determine the pagination behavior required for large responses and how clients request pages; done means /search supports paginated results. No file or test is named, so further repository research is needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100