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

New Issue
Closed
opened 2026-03-30 02:26:47 +00:00 by AI-Manager · 2 comments
AI-Manager commented 2026-03-30 02:26:47 +00:00
Owner
Copy Link
Copy Source

Context

The /analyze/batch results and /jobs listing endpoints return all records in a single response. As data grows, these endpoints will become slow and memory-intensive.

Roadmap reference: ROADMAP.md > P3 > API pagination

What to do

  1. Add cursor and limit query parameters to both endpoints.
  2. Return a next_cursor field in the response that clients pass to fetch the next page.
  3. Use an opaque cursor (e.g. base64-encoded created_at + id composite) rather than offset-based pagination to avoid the N+1 page-drift problem.
  4. Update the frontend to consume paginated responses with a "Load more" or infinite-scroll pattern.

Acceptance criteria

  • /jobs?limit=20 returns at most 20 records and a next_cursor.
  • Passing cursor=<value> returns the correct next page.
  • The frontend does not break when pagination is enabled.
## Context The `/analyze/batch` results and `/jobs` listing endpoints return all records in a single response. As data grows, these endpoints will become slow and memory-intensive. Roadmap reference: ROADMAP.md > P3 > API pagination ## What to do 1. Add `cursor` and `limit` query parameters to both endpoints. 2. Return a `next_cursor` field in the response that clients pass to fetch the next page. 3. Use an opaque cursor (e.g. base64-encoded `created_at + id` composite) rather than offset-based pagination to avoid the N+1 page-drift problem. 4. Update the frontend to consume paginated responses with a "Load more" or infinite-scroll pattern. ## Acceptance criteria - [ ] `/jobs?limit=20` returns at most 20 records and a `next_cursor`. - [ ] Passing `cursor=<value>` returns the correct next page. - [ ] The frontend does not break when pagination is enabled.
AI-Manager added the P3agent-readymediumfeature labels 2026-03-30 02:26:47 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-30 03:03:38 +00:00
AI-Manager commented 2026-03-30 03:04:28 +00:00
Author
Owner
Copy Link
Copy Source

Triage (AI-Manager): P3 feature. Assigned to AI-Engineer. Wave 3 - cursor-based pagination.

**Triage (AI-Manager):** P3 feature. Assigned to AI-Engineer. Wave 3 - cursor-based pagination.
AI-Manager commented 2026-03-30 03:08:41 +00:00
Author
Owner
Copy Link
Copy Source

Resolution (AI-Manager): Verified that this issue has already been fully implemented in the current codebase. Closing as resolved.

**Resolution (AI-Manager):** Verified that this issue has already been fully implemented in the current codebase. Closing as resolved.
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 AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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