Skip to content

Page through a table's rows in the Tables explorer - #9153

Merged
cstns merged 3 commits into
9147-tables-data-paginationfrom
9148-tables-ui-pagination
Nov 16, 2026
Merged

cstns merged 3 commits into
9147-tables-data-paginationfrom
9148-tables-ui-pagination

Conversation

@cstns

@cstns cstns commented Nov 11, 2026

Copy link
Copy Markdown
Contributor

Closes #9148
Closes #6428

Stacked on #9150, which adds paging to the table data endpoint.

Opening a table in the Tables explorer showed its first 10 rows and nothing else, with no next page, no row count and no hint that more existed.

The grid now has a paging footer: a rows per page picker (10, 25, 50 or 100, starting at 25), the range being shown out of the table's total, and page buttons with previous, next and a jump to the first and last page. It's the pagination ff-data-table already has and the instances list uses, so there's no new component here. The page and page size are kept in the Tables store, which is what lets Refresh reload the page you're on. Picking another table starts back on page 1 and keeps the page size.

Like on the instances list, the footer only shows once a table has more rows than fit on one page, and the range reads "26–50 of 1284" rather than the "Showing 26 to 50 of 1,284" in the #9026 mockup.

Clicking a column header no longer sorts. It only ever reordered the rows on screen, which reads as sorting the table and isn't, and with pages that gets worse. Proper sorting is the next piece of #9025.

The docs line saying the explorer shows the first 10 rows is updated too.

Covered by the store and rows list specs. Also checked in the browser against a local 1,284 row table and a 7 row one: next, jump to the last page, Refresh on the last page, changing the page size, and switching between tables.

@cstns cstns self-assigned this Nov 11, 2026
@cstns
cstns added this pull request to stack #9154 November 11, 2026 12:08
@codecov

codecov Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.61%. Comparing base (6d8d481) to head (2460f77).

Additional details and impacted files
@@                     Coverage Diff                      @@
##           9147-tables-data-pagination    #9153   +/-   ##
============================================================
  Coverage                        80.61%   80.61%           
============================================================
  Files                              477      477           
  Lines                            26331    26331           
  Branches                          7012     7012           
============================================================
  Hits                             21227    21227           
  Misses                            5104     5104           
Flag Coverage Δ
backend 80.61% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Comment thread frontend/src/stores/product-tables.js Resolved
@cstns
cstns force-pushed the 9148-tables-ui-pagination branch from aa09233 to 331228e Compare November 12, 2026 09:06
@cstns
cstns requested a review from andypalmi November 12, 2026 09:10
cstns and others added 3 commits November 13, 2026 12:38
The explorer only showed the first 10 rows of a table with no way to reach the rest. The grid now has the paging footer the instances list uses, with a rows per page picker, the range being shown out of the table total, and page buttons. The page and page size live in the Tables store so Refresh reloads the current page, and picking another table starts back on the first page.

Sorting by clicking a column header is gone for now, since it only reordered the rows on screen.
Co-authored-by: Andrea Palmieri <76187074+andypalmi@users.noreply.github.com>
Clicking two pages quickly could let the older response land last, leaving the grid on one page while the footer showed another, and the first response to arrive turned the loading state off while the other was still on its way. A page response is now dropped when the page or page size changed while it was loading, and only the most recently chosen page clears the loading state. Also adds tests for falling back to the last page when the table shrinks.
@cstns
cstns force-pushed the 9148-tables-ui-pagination branch from 331228e to 2460f77 Compare November 13, 2026 10:42
@cstns

cstns commented Nov 13, 2026

Copy link
Copy Markdown
Contributor Author

What to look at: the footer under the grid. Page size picker on the left, the "26 to 50 of 57" range and the page buttons on the right. It only shows when the table has more than one page, and column sorting is gone since only one page is loaded.

9153-pager-close-up 9153-pager-page-2

@cstns
cstns merged commit 9708f18 into main Nov 16, 2026
54 of 64 checks passed
@cstns
cstns deleted the 9148-tables-ui-pagination branch November 16, 2026 13:27

This branch was successfully deployed

1 active deployment
staging — 2460f77f Deployed Nov 16, 2026 by cstns via Remove application #13096
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants