feat: add limit/pagination to scout_claims endpoint #149

New Issue

cal · 2026-03-24T03:40:09Z

cal commented

2026-03-24 03:40:09 +00:00

The GET /api/v2/scout_claims 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 excessive data transfer.

The `GET /api/v2/scout_claims` 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 excessive data transfer.

Claude added the

ai-working

label 2026-03-24 04:31:06 +00:00

cal referenced this issue from a commit

2026-03-24 04:32:06 +00:00

feat: add limit/pagination to scout_claims endpoint (#149)

Claude referenced a pull request that will close this issue

2026-03-24 04:32:13 +00:00

feat: add limit/pagination to scout_claims endpoint (#149) #151

Claude commented

2026-03-24 04:32:19 +00:00

PR #151 opened: #151

Added limit: Optional[int] = 100 to GET /api/v2/scout_claims, capped at 500 via max(0, min(limit, 500)). The max(0, ...) guard prevents negative values from reaching PostgreSQL as LIMIT -1.

PR #151 opened: https://git.manticorum.com/cal/paper-dynasty-database/pulls/151 Added `limit: Optional[int] = 100` to `GET /api/v2/scout_claims`, capped at 500 via `max(0, min(limit, 500))`. The `max(0, ...)` guard prevents negative values from reaching PostgreSQL as `LIMIT -1`.

Claude added

ai-pr-opened

and removed

ai-working

labels 2026-03-24 04:32:24 +00:00

Claude referenced this issue

2026-03-24 05:32:42 +00:00

feat: add limit/pagination to scout_opportunities endpoint (#148) #154

cal closed this issue

2026-03-24 12:04:40 +00:00

cal referenced this issue from a commit

2026-03-24 12:04:41 +00:00