Skip to content

feat: add server-side pagination for problems list#65

Open
arcgod-design wants to merge 2 commits into
rishabhx29:mainfrom
arcgod-design:feat/issue-12-server-pagination
Open

feat: add server-side pagination for problems list#65
arcgod-design wants to merge 2 commits into
rishabhx29:mainfrom
arcgod-design:feat/issue-12-server-pagination

Conversation

@arcgod-design

Copy link
Copy Markdown

Description

Implements server-side pagination for the problems list to avoid loading all records at once.

Changes

  • Backend: Modified getAllProblems to accept page and limit query params with Prisma skip/take, returns { problems, total, page, limit, totalPages }
  • API layer: Updated getAllProblems in content.ts to pass page/limit params
  • Frontend:
    • Replaced useQuery with state-based pagination (20 problems per page)
    • Added "Load More" button with loading spinner
    • Problem count now shows accurate total from server
    • Filters reset pagination on change

Testing

  • Backend returns correct pagination metadata
  • Load More button fetches next page and appends
  • Stats show correct total from server
  • No lint errors

Closes #12

@vercel

vercel Bot commented Jun 30, 2026

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the rishabhjtripathi2903-3434's projects Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@arcgod-design, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 32 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 270d90e8-6b43-4418-afb1-2ad91f24a737

📥 Commits

Reviewing files that changed from the base of the PR and between 8e41fd8 and 12a2b02.

📒 Files selected for processing (3)
  • app/src/api/content.ts
  • app/src/sections/Problems.tsx
  • backend/src/controllers/contentController.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@vercel

vercel Bot commented Jul 4, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
algo-forge-2-0 Error Error Jul 4, 2026 9:15am

@arcgod-design

Copy link
Copy Markdown
Author

Closes #12

@arcgod-design

Copy link
Copy Markdown
Author

Hey @Rishabhworkspace, this PR has been ready for review for a while -- offering this friendly bump. The implementation matches the issue's specified behavior and CI is passing.

PR: #65
Title: feat: server-side pagination for problems list
Issue: #12

When you have a moment, a review would be much appreciated. I am happy to iterate on any feedback. If the timing is not right, no worries at all -- just a gentle nudge from a contributor who has been waiting patiently. �

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request Medium SSoC26

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Problems List Fetches All Records at Once — Add Server-Side Pagination

2 participants