[9.x] Adds ability to have simplePaginate() $perPage parameter as callable with access to $total #42840
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.
The feature adds the ability to have
$perPage
as a callback closure with access to $total.There might be a scenario when you want to use different/dynamic per page depending on the total count of records.
For example, in a list of products, with the above snippet, it will load all ~110 products if there are less than or equal to 110 products in total. Else, defaults to 100 as usual. So that, there won't be just a few items sitting around on the second page.
Similarly, if we want to have exact 4 pages, we can provide a dynamic per page value like such:
And, of course, the normal simplePaginate(10) will still work.
This PR is a same this PR #42429 put in
simplePaginate