cleodora-forecasting / cleodora-forecasting/cleodora
[Epic] Pagination for forecasts
- Dominant language
- Go
- Stars
- 24
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
```[tasklist]
### Tasks
- [ ] API: Pagination for forecasts
- [ ] Frontend: Paginate the table of forecasts
- [ ] cleoc: Paginate the list of forecasts
```
Having all forecasts being displayed in one table stops being feasible after ~100. The ability to paginate is a must. I find Continuous Scrolling rather annoying in practice and in particular with these types of applications where you do want a sense of how many items there are it is not helpful.
Contributor guide
Research direction
Start by tracing how forecasts are listed through the API, the frontend forecast table, and the cleoc forecast list. Determine how each of the three task areas currently loads forecasts. Done means all three areas paginate the results rather than displaying the entire forecast collection at once.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, graphql, react, typescript
- Domain
- api, frontend, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100