microsoft / microsoft/AzureTRE
Resource Pagination
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
Some resource types may end up in the 100's. We need to paginate these results with skip and take options
- Implement skip + take on all resource types in API
- Implement pagination on all resource lists in UI
Initial page size of 20
Question for @marrobi - should we be following a HATEOAS approach and giving a next link in the page of results, or are we not worried about that?
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
The issue names no files or tests. Start by locating the API resource-list endpoints and the UI components that render resource lists, then trace how list requests and responses are handled. Done means all resource types accept skip and take, all UI resource lists paginate with an initial page size of 20, and the pagination approach is settled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100