Restore full game search pagination #998
No reviewers
Labels
No labels
automated
code-quality
component: admin dashboard
component: backend
component: billing
component: content management
component: faqs
component: game genres
component: game lists
component: game reviews
component: game search
component: games
component: internal notifications
component: platforms
component: security
component: tests
component: user api
component: user badges
component: user blogs
component: user consoles
component: user favorites
component: user friends
component: user notifications
component: user profiles
component: user site notifications
component: user wishlists
component: web design
dependencies
javascript
php
priority
high
priority
low
priority
medium
security-hotspot
source: codex
source: sonarqube
status
awaiting feedback
status
backlog
status
done
status
in progress
status
in queue
status
in review
status
needs codex review
status
needs investigation
status
wontfix
type: bug
type: documentation
type: feature
type: improvement
type: regression
type: task
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MyVideoGameList/myvideogamelist.com!998
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/issue-992-search-pagination"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Restore exact game-search totals, result ranges, page counts, and direct page navigation on desktop and mobile.
Use Laravel length-aware pagination with the existing covering index and page-only card loading. Match the requested joined paginator styling, preserve query parameters and ranking, and handle empty, single-page, and out-of-range results.
Verification: 77 focused search and pending-game workflow tests passed (797 assertions); Pint, PHPStan, asset build, and diff checks passed. Playwright verified desktop/mobile rendering and direct navigation without browser errors. Read-only production MariaDB samples measured counts at 36–53 ms using the covering index; full-request production latency remains a post-deployment check.
Fixes #992
c64741363d360b5f33b9360b5f33b9917732a135