feat: add limit/pagination to results endpoint #137

New Issue

cal · 2026-03-24T03:39:54Z

cal commented

2026-03-24 03:39:54 +00:00

The GET /api/v2/results endpoint returns all records with no limit parameter. Add an optional limit: int query param (default 100, max 500).

Found during smoke test development — endpoints without limits cause timeouts and excessive data transfer.

The `GET /api/v2/results` endpoint returns all records with no `limit` parameter. Add an optional `limit: int` query param (default 100, max 500). Found during smoke test development — endpoints without limits cause timeouts and excessive data transfer.

Claude added the

ai-working

label 2026-03-24 10:01:04 +00:00

cal referenced this issue from a commit

2026-03-24 10:02:40 +00:00

feat: add limit/pagination to results endpoint (#137)

Claude referenced a pull request that will close this issue

2026-03-24 10:02:47 +00:00

feat: add limit/pagination to results endpoint (#137) #163

Claude removed the

ai-working

label 2026-03-24 10:02:52 +00:00

Claude commented

2026-03-24 10:02:55 +00:00

PR opened: #163

Added limit: int = 100 to GET /api/v2/results, capped at 500 via max(0, min(limit, 500)). Applied after all filters, before the CSV/JSON branch — both response paths honour the limit.

PR opened: https://git.manticorum.com/cal/paper-dynasty-database/pulls/163 Added `limit: int = 100` to `GET /api/v2/results`, capped at 500 via `max(0, min(limit, 500))`. Applied after all filters, before the CSV/JSON branch — both response paths honour the limit.

Claude added the

ai-pr-opened

label 2026-03-24 10:02:58 +00:00

cal closed this issue

2026-03-24 12:08:03 +00:00

cal referenced this issue from a commit

2026-03-24 12:08:03 +00:00

Merge pull request 'feat: add limit/pagination to results endpoint (#137)' (#163) from issue/137-feat-add-limit-pagination-to-results-endpoint into main

Sign in to join this conversation.