hardly depend on a Page object to make the pager iterable #17
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.
Ease construction of a pager object via Pager::fromResult.
I changed the way the Pager depends on Page. Now you have to pas it a
Page
instance,but it eases the end-to-end usage: you only have to use
Pager::fromResult($result, $page, $numberPerPage)
and you have a fully iterable pager:
WDYT?