Fix bounties page first-paint pagination regression#1046
Closed
0xh4rry wants to merge 1 commit into
Closed
Conversation
Collaborator
|
Duplicate of #1028 which is better scoped/implemented. Closing. |
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.
Fixes #1027.\n\n## Summary\n- restore bounded rendering for the bounties list by paging the sorted issue set\n- render 12 cards in card view or 10 rows in list view using the existing issues view defaults\n- add prev/next pagination below both card and table render paths\n- reset pagination when filter, search, sort, or view mode changes\n\n## Verification\n- npm run lint\n- npm run build\n\n## Notes\nThis keeps the change scoped to the regression from PR #983: both render paths now receive a paginated slice instead of the full sorted issue array.