forked from 0xWheatyz/SPARC
Add cursor-based pagination to /analyze/batch and /jobs endpoints #374
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 in a single response. As the dataset grows, this becomes slow and memory-intensive for both the server and the client.Work
cursor+limitquery parameters) on:GET /jobs— list of all batch jobs.GET /analyze/batch— if it returns historical batch results.next_cursorfield in responses when more results are available.Acceptance Criteria
GET /jobs?limit=20returns at most 20 results and anext_cursor.GET /jobs?limit=20&cursor=<token>returns the next page.next_cursoris null.Reference
Roadmap item: P3 — API pagination.
[Triage] Already implemented in main. /jobs endpoint supports cursor-based pagination with limit and cursor parameters. Closing as resolved.