fix: allow page length 2500 (backport #25062) #25484
Merged
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.
Multiple of our customers have recently expressed their struggle with loading many records: select page length 500, then klick load more, scroll down, load more, scroll down, ...
A long page length is useful for reports, when your filters result in a couple thousand records and you need to load and check (or print) all rows.
Why 2500? We always have 5x increments: 20, 100, 500, 2500
On my development site, the request take 115 ms for the server to process and about 4 seconds for the browser to render. This seems acceptable.
This is an automatic backport of pull request #25062 done by Mergify.