forked from 0xWheatyz/SPARC
Add cursor-based pagination to /analyze/batch and /jobs endpoints #397
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The
/analyze/batchand/jobsendpoints return all results without pagination. As the dataset grows this becomes impractical — large payloads slow the UI and can exhaust memory.Work
/jobsand any list endpoints under/analyze/batch.limitandcursor(orpage/offset) query parameters.next_cursor(or equivalent) in the response so clients can fetch the next page.Acceptance Criteria
GET /jobs?limit=20returns at most 20 results and a cursor for the next page.GET /jobs?limit=20&cursor=<value>returns the next page.Reference
Roadmap item: P3 — API pagination.
Closing as already implemented. Cursor-based pagination is implemented on /jobs endpoint with next_cursor field and PaginatedJobsResponse model.