[5.3] LengthAwarePaginator custom pageName and currentPage #15870
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.
Hi there.
New to Laravel, 3 weeks in and absolutely love it.
Ran into minor problem using multiple
LengthAwarePaginator
s on a single page with alternatepageName
properties. Traced problem to the attached proposed change.When checking the current page for a
LengthAwarePaginator
instance, any non-defaultpageName
is not sent toresolveCurrentPage
and as such 1 is always returned (unlesspageName
of 'page' is used.Andrew