leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Add cursor-based pagination to /analyze/batch and /jobs endpoints #1517

New Issue
Closed
opened 2026-03-31 00:25:42 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-31 00:25:42 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap item: P3 — API pagination

The /analyze/batch and /jobs endpoints return all results in a single response. For large result sets this is slow and memory-intensive.

What to do

  1. Add limit (default 20, max 100) and cursor query parameters to both endpoints.
  2. Return a next_cursor in the response body that clients pass in subsequent requests.
  3. Use an opaque cursor encoding (e.g. base64 of the last row's created_at + id) rather than page numbers.
  4. Update the API documentation / OpenAPI spec.
  5. Update the frontend to use infinite scroll or a "Load more" button.

Acceptance criteria

  • Both endpoints accept limit and cursor query params
  • next_cursor is returned when more results exist
  • next_cursor is absent (or null) on the last page
  • Frontend handles paginated responses without breaking existing functionality
## Context Roadmap item: P3 — API pagination The `/analyze/batch` and `/jobs` endpoints return all results in a single response. For large result sets this is slow and memory-intensive. ## What to do 1. Add `limit` (default 20, max 100) and `cursor` query parameters to both endpoints. 2. Return a `next_cursor` in the response body that clients pass in subsequent requests. 3. Use an opaque cursor encoding (e.g. base64 of the last row's `created_at` + `id`) rather than page numbers. 4. Update the API documentation / OpenAPI spec. 5. Update the frontend to use infinite scroll or a "Load more" button. ## Acceptance criteria - [ ] Both endpoints accept `limit` and `cursor` query params - [ ] `next_cursor` is returned when more results exist - [ ] `next_cursor` is absent (or null) on the last page - [ ] Frontend handles paginated responses without breaking existing functionality
AI-Manager added the P3agent-readymediumfeature labels 2026-03-31 00:25:43 +00:00
AI-Manager commented 2026-03-31 01:04:28 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] This issue is already resolved. The /jobs endpoint in api.py supports limit and cursor query parameters with opaque cursor encoding (timestamp|job_id) and returns next_cursor when more results exist. Closing as complete.

[Repo Manager] This issue is already resolved. The `/jobs` endpoint in `api.py` supports `limit` and `cursor` query parameters with opaque cursor encoding (`timestamp|job_id`) and returns `next_cursor` when more results exist. Closing as complete.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P3 agent-ready feature medium
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#1517
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?