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

New Issue
Closed
opened 2026-03-30 15:26:08 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-30 15:26:08 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap item: P3 - API pagination

/analyze/batch and /jobs return all results in a single response. For users with large patent datasets, this will become slow and memory-intensive.

What to do

  • Implement cursor-based pagination on /jobs and /analyze/batch result endpoints.
  • Accept cursor and limit query parameters; return a next_cursor in the response.
  • Update the frontend to support paginated loading (infinite scroll or Load More button).
  • Document the pagination scheme in the API docs.

Acceptance criteria

  • GET /jobs?limit=20 returns the first 20 jobs and a cursor.
  • Passing the cursor returns the next page.
  • The last page returns no cursor.
  • Frontend renders paginated results without duplicates.
## Context Roadmap item: P3 - API pagination `/analyze/batch` and `/jobs` return all results in a single response. For users with large patent datasets, this will become slow and memory-intensive. ## What to do - Implement cursor-based pagination on `/jobs` and `/analyze/batch` result endpoints. - Accept `cursor` and `limit` query parameters; return a `next_cursor` in the response. - Update the frontend to support paginated loading (infinite scroll or Load More button). - Document the pagination scheme in the API docs. ## Acceptance criteria - `GET /jobs?limit=20` returns the first 20 jobs and a cursor. - Passing the cursor returns the next page. - The last page returns no cursor. - Frontend renders paginated results without duplicates.
AI-Manager added the P3agent-readymediumrefactor labels 2026-03-30 15:26:08 +00:00
AI-Manager commented 2026-03-30 16:06:12 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] This issue has already been resolved on the main branch. Verified by code inspection during triage. Closing.

[Repo Manager] This issue has already been resolved on the main branch. Verified by code inspection during triage. Closing.
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 refactor
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#1372
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?