-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
feat(replay): Add pagination to Playlist view #105701
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
8fa4636 to
3c3aded
Compare
| {pageLinks ? ( | ||
| <StyledPagination | ||
| pageLinks={pageLinks} | ||
| onCursor={(cursor, path, searchQuery) => { | ||
| navigate({ | ||
| pathname: path, | ||
| query: {...searchQuery, cursor}, | ||
| }); | ||
| }} | ||
| /> | ||
| ) : null} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TBD, but if we want scrolling to work properly in playlist tab, we need to embed pagination into the table, otherwise we can't internally scroll the table. since we have:
| alert |
| table |
| pagination |
ideally, alert should be sticky at the top, along with the table headers, and pagination should only be visible when we scroll to the last row in the table.
In order to have table headers sticky, we would need the scroll to be internal to the table, which means the only way to see pagination only when we reach the last row in the table is for pagination to be embedded in the table. Otherwise, we would need pagination to always be visible as well, which is kind of a waste of pixels.
This adds our normal pagination at the end of the replays table in the Playlist view
79f9930 to
85c7fff
Compare
…it is covered by header)
This adds our normal pagination at the end of the replays table in the Playlist view