[5.6] Paginators should be built from Contracts #21852
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Improve documentation :D
Signed-off-by: Jesse Schutt <[email protected]>
Follow up to laravel#19328, paginators should not only be built of the container, they should use the interface. This is more correct and gives developers more flexibility in their implementation.
|
You have broken the tests |
tillkruss
changed the title
tillkruss
changed the title
|
I've changed the branch to 5.6. You need to rebase and fix the tests. |
|
There are other commits in the PR. |
|
@grashoper20 Try resubmitting this to the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Follow up to #19328, paginators should not only be built of the container, they should use the interface. This is more correct and gives developers more flexibility in their implementation.