Add Pagination to Assigned Pages and All Pages

[weatherpattern]

All Pagination to the UI.

Are there any React libraries that use this easily? If you need me to draw up some UX for this, let me know.

[lightandluck]

I think it should be straight-forward to create a component for this without using a library. If you have ideas for the UX that would be great to add.

[weatherpattern]

@lightandluck How about something like this? (Also let me know if you need more annotation on the specs.) If we want to break it up into parts, in order of importance:

• The pagination footer should lock in place at the bottom of the browser, like the header does at the top. The list slides "underneath" the footer, so that the footer is alway visible.

• Page selector Click on a page number, jumps to the page. If 7 pages or less, button for 1-7 appear. If 8 pages or more, show buttons for 1,2,3, and the last 3 pages. If 1st page is being viewed, left arrow does not appear. If last page is being viewed, right arrow does not appear.

• Page: (Jump to page) User enters a page number and click on Go, jumps to the page entered. (If the user enters a number larger than the number of pages, go to the last page. Entering

• Show: (select number of urls to display per page) User can select from 25, 50, 100, 200 pages. Once selected, the page will automatically reload with the number of links per page. Default is 50 urls.

[Mr0grog]

Honest question: would infinite scrolling be any better here?

[weatherpattern]

Good question. I thought about that. A challenge with infinite scrolling, is when the user has downloaded a potentially long list of rows, and then the user wants to navigating backwards/ upwards. If she is skimming say 300-400 rows and then needs to refer back to something in row 100, it can be difficult to find. Maybe she could use search, maybe this is an edge case, maybe it's anecdotal and my personal bias, but I have experienced this issue in Instagram and Medium. I'll add this to the agenda.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in seven days if no further activity occurs. If it should not be closed, please comment! Thank you for your contributions.

[Mr0grog]

Not high priority at the moment (analysts are still mostly using sheets), but critical as soon as we want to get away from task sheets generated each week.