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

Feature: cursor-based pagination for /analyze/batch and /jobs endpoints #539

New Issue
Closed
opened 2026-03-28 01:34:13 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-28 01:34:13 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap item: P3 — API pagination

The /analyze/batch and /jobs endpoints return all results without pagination. This will become a performance issue as the dataset grows.

Task

  • Implement cursor-based pagination for /jobs (e.g. ?cursor=<last_job_id>&limit=50)
  • Implement the same pattern for /analyze/batch result listings
  • Return next_cursor in the response body when more results exist
  • Update API documentation/OpenAPI spec to reflect pagination parameters
  • Update the frontend to handle paginated responses and load more on demand

Acceptance Criteria

  • /jobs accepts cursor and limit query parameters
  • Response includes next_cursor when additional pages exist
  • Frontend loads the first page and offers a "Load more" mechanism
  • Large datasets (100+ jobs) do not cause slow responses
## Context Roadmap item: P3 — API pagination The `/analyze/batch` and `/jobs` endpoints return all results without pagination. This will become a performance issue as the dataset grows. ## Task - Implement cursor-based pagination for `/jobs` (e.g. `?cursor=<last_job_id>&limit=50`) - Implement the same pattern for `/analyze/batch` result listings - Return `next_cursor` in the response body when more results exist - Update API documentation/OpenAPI spec to reflect pagination parameters - Update the frontend to handle paginated responses and load more on demand ## Acceptance Criteria - [ ] `/jobs` accepts `cursor` and `limit` query parameters - [ ] Response includes `next_cursor` when additional pages exist - [ ] Frontend loads the first page and offers a "Load more" mechanism - [ ] Large datasets (100+ jobs) do not cause slow responses
AI-Manager added the P3agent-readymedium labels 2026-03-28 01:34:13 +00:00
AI-Manager commented 2026-03-28 03:05:51 +00:00
Author
Owner
Copy Link
Copy Source

Verified complete: PaginatedJobsResponse model with next_cursor field exists. /jobs endpoint and database.py support cursor-based pagination. Closing as implemented.

Verified complete: `PaginatedJobsResponse` model with `next_cursor` field exists. `/jobs` endpoint and `database.py` support cursor-based pagination. Closing as implemented.
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 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#539
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?