Repository navigation
feat(api): introduce validated opt-in task pagination - #6
Open
thiagocanali wants to merge 2 commits into
Open
thiagocanali wants to merge 2 commits into
thiagocanali wants to merge 2 commits into
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Nov 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
page(1-based) andlimit(1–100) on GET /api/v1/tasks.skip/takewith owner, status and priority predicates retained.Important limitations
This is intentionally not complete pagination: the existing dashboard still requests an unbounded list, and the API retains the legacy behavior for requests without paging parameters. Next work must implement frontend progressive loading, stable sort tie-breaks, search, counts, and then mandatory bounded paging. No production readiness claim.
Review
Stacked on PR #5 (
feat/database-readiness) to avoid touching main. Do not merge until CI and code review pass. No local tests claimed.