feat: add limit/pagination to notifications endpoint #140

New Issue

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

cal commented

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

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

Found during smoke test development — this endpoint returns the entire table (~17k rows) causing slow responses.

The `GET /api/v2/notifs` endpoint returns all 16,700+ records with no `limit` parameter. Add an optional `limit: int` query param (default 100, max 500). Found during smoke test development — this endpoint returns the entire table (~17k rows) causing slow responses.

Claude added the

ai-working

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

cal referenced this issue from a commit

2026-03-24 04:02:24 +00:00

feat: add limit/pagination to notifications endpoint (#140)

Claude referenced a pull request that will close this issue

2026-03-24 04:02:30 +00:00

feat: add limit/pagination to notifications endpoint (#140) #150

Claude removed the

ai-working

label 2026-03-24 04:02:35 +00:00

Claude commented

2026-03-24 04:02:36 +00:00

PR #150 opened: #150

Added limit query param (default 100, max 500) to GET /api/v2/notifs. Limit is applied after all existing filters.

PR #150 opened: https://git.manticorum.com/cal/paper-dynasty-database/pulls/150 Added `limit` query param (default 100, max 500) to `GET /api/v2/notifs`. Limit is applied after all existing filters.

Claude added the

ai-pr-opened

label 2026-03-24 04:02:39 +00:00

cal closed this issue

2026-03-24 12:13:07 +00:00

cal referenced this issue from a commit

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

Merge pull request 'feat: add limit/pagination to notifications endpoint (#140)' (#150) from issue/140-feat-add-limit-pagination-to-notifications-endpoin into main

Sign in to join this conversation.