fix(component): persist selection across TableNext pages #985
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.
What?
Enables
TableNext
to persist selected items across pagination.Why?
For each page, we were returning the indexes of items without accounting for pagination. If you were on page 2, the indexes you were getting back were
{ 0: true, 1: true, 2.0: true, ...etc }
. This made it difficult to both Selected all products across pages and persist selected items across pages. This update aligns with our vision of moving toward using@tanstack/react-table
or other similar headless table API's to power ourTableNext
component.Screenshots/Screen Recordings
Screen.Recording.2022-09-26.at.15.11.54.mov
Testing/Proof
Here's the
dev.tsx
page I used if you want to test it out yourself: