-
Notifications
You must be signed in to change notification settings - Fork 356
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
Fix table pagination setting #9324
Fix table pagination setting #9324
Conversation
4121032
to
4a5b3d4
Compare
@@ -273,7 +273,7 @@ const setPaging = (settings, start, perPage) => ({ | |||
const computePagination = (settings) => ({ | |||
page: settings.current, | |||
perPage: settings.perpage, | |||
perPageOptions: [10, 20, 50, 100, 200, 500, 1000], | |||
perPageOptions: [5, 10, 20, 50, 100, 200, 500, 1000], |
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.
As discussed, this was added to match the Setting side, where 5 is already a choice.
Note, the ruby changes were removed from this pr as we decided the report and report detail page will use the reports items per page value. If we want the report list to use the list value then as a follow up pr we would need to change the tables dbname value. |
Backported to
|
…ting Fix table pagination setting (cherry picked from commit f94b162)
Fixed issues with table pagination settings.
Before:
The default items per page on the settings page was not actually being applied on the tables in the UI.
As seen here the table defaults to 20 items per page even though in the settings it was set to 10.
Also, 5 items per page is not an option here even though it is on the settings page.
After: