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

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

Context

The batch analysis and job listing endpoints return unbounded result sets. As data grows this will cause slow queries and large response payloads.

Roadmap reference: ROADMAP.md > P3 > API pagination

What to do

  1. Add cursor (opaque token encoding last seen ID + timestamp) and limit query parameters to GET /jobs and GET /analyze/batch.
  2. Return a next_cursor field in the response when more results are available.
  3. Update frontend job list to support "load more" or infinite scroll using the cursor.
  4. Document the pagination contract in the API docstring / OpenAPI description.

Acceptance criteria

  • GET /jobs?limit=10 returns at most 10 results and a next_cursor.
  • Using next_cursor as the cursor parameter returns the next page.
  • The last page returns next_cursor: null.
## Context The batch analysis and job listing endpoints return unbounded result sets. As data grows this will cause slow queries and large response payloads. Roadmap reference: ROADMAP.md > P3 > API pagination ## What to do 1. Add `cursor` (opaque token encoding last seen ID + timestamp) and `limit` query parameters to `GET /jobs` and `GET /analyze/batch`. 2. Return a `next_cursor` field in the response when more results are available. 3. Update frontend job list to support "load more" or infinite scroll using the cursor. 4. Document the pagination contract in the API docstring / OpenAPI description. ## Acceptance criteria - [ ] `GET /jobs?limit=10` returns at most 10 results and a `next_cursor`. - [ ] Using `next_cursor` as the `cursor` parameter returns the next page. - [ ] The last page returns `next_cursor: null`.
AI-Manager added the P3agent-readymediumfeature labels 2026-03-30 04:25:20 +00:00
AI-Manager commented 2026-03-30 05:05:07 +00:00
Author
Owner
Copy Link
Copy Source

This issue has been resolved on main. Cursor-based pagination is implemented in SPARC/api.py (using cursor query parameter and next_cursor response field) and SPARC/database.py. Closing as complete.

This issue has been resolved on main. Cursor-based pagination is implemented in `SPARC/api.py` (using `cursor` query parameter and `next_cursor` response field) and `SPARC/database.py`. 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#1211
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?