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 #822

New Issue
Closed
opened 2026-03-29 01:24:46 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-29 01:24:46 +00:00
Owner
Copy Link
Copy Source

Background

The /analyze/batch and /jobs endpoints return all results in a single response. As the dataset grows this will become slow and memory-intensive.

What to do

  1. Implement cursor-based pagination on GET /jobs using an after cursor parameter and a limit parameter (default 20, max 100)
  2. The response should include a next_cursor field (null if no more pages)
  3. Document the pagination scheme in the API docstring / OpenAPI description
  4. Update the frontend jobs list to load more results when the user scrolls to the bottom or clicks "Load more"

Acceptance criteria

  • GET /jobs?limit=10 returns at most 10 results with a next_cursor
  • GET /jobs?after=<cursor> returns the next page
  • Frontend loads additional pages on demand
  • Total count is still accessible (e.g., via a GET /jobs/count endpoint or response header)

References

Roadmap item: P3 -- API pagination

## Background The `/analyze/batch` and `/jobs` endpoints return all results in a single response. As the dataset grows this will become slow and memory-intensive. ## What to do 1. Implement cursor-based pagination on `GET /jobs` using an `after` cursor parameter and a `limit` parameter (default 20, max 100) 2. The response should include a `next_cursor` field (null if no more pages) 3. Document the pagination scheme in the API docstring / OpenAPI description 4. Update the frontend jobs list to load more results when the user scrolls to the bottom or clicks "Load more" ## Acceptance criteria - `GET /jobs?limit=10` returns at most 10 results with a `next_cursor` - `GET /jobs?after=<cursor>` returns the next page - Frontend loads additional pages on demand - Total count is still accessible (e.g., via a `GET /jobs/count` endpoint or response header) ## References Roadmap item: P3 -- API pagination
AI-Manager added the P3agent-readymediumfeature labels 2026-03-29 01:24:46 +00:00
AI-Manager commented 2026-03-29 02:07:01 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved and merged into main via PR #59 (feat: add cursor-based pagination to /jobs endpoint). Closing as completed.

This issue has already been resolved and merged into main via PR #59 (feat: add cursor-based pagination to /jobs endpoint). Closing as completed.
AI-Manager commented 2026-03-29 02:07:52 +00:00
Author
Owner
Copy Link
Copy Source

This issue has already been resolved and merged into main via PR #59 (feat: add cursor-based pagination to /jobs endpoint). Closing as completed.

This issue has already been resolved and merged into main via PR #59 (feat: add cursor-based pagination to /jobs endpoint). Closing as completed.
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#822
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?