Repository navigation
Page through a table's rows in the Tables explorer - #9153
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 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
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
cstns
force-pushed
the
9148-tables-ui-pagination
branch
from
November 11, 2026 14:50
54e7a93 to
2df97cb
Compare
cstns
marked this pull request as ready for review
November 11, 2026 15:23
andypalmi
reviewed
Nov 11, 2026
cstns
force-pushed
the
9148-tables-ui-pagination
branch
from
November 12, 2026 09:06
aa09233 to
331228e
Compare
andypalmi
approved these changes
Nov 12, 2026
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
force-pushed
the
9148-tables-ui-pagination
branch
from
November 13, 2026 10:42
331228e to
2460f77
Compare
Contributor
Author
This branch was successfully deployed
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
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.

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-tablealready 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.