[BUG] Infinite/incorrect pagination skip calculation - #273
Merged
Conversation
|
@Aditya8369 is attempting to deploy a commit to the omkarhole's projects Team on Vercel. A member of the Team first needs to authorize it. |
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
2 participants
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.
Fixed infinite/incorrect pagination skip calculation in frontend/src/components/ReferralList.jsx.
Removed nextPage / nextSearch indirection.
fetchReferrals() now sends explicit params.page (and params.search when present) to /api/referrals.
Local pagination page is now set strictly from response.data.pagination.page.
Next/Previous no longer drift from server pagination.
Search/filter submit resets pagination deterministically to page 1.
Build verification: cd frontend && npm run build ✅ succeeded.
closes #248