-
Notifications
You must be signed in to change notification settings - Fork 347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Laravel-5.0] Add the support for Laravel 5 paginator #153
[Laravel-5.0] Add the support for Laravel 5 paginator #153
Conversation
This doesn't work on php 5.3. The dependencies don't install. |
@GrahamCampbell I know that, it's because |
Composer has a flag you can run it with to get around this you know. :) |
Edit the travis file to run composer with |
Good to know, should i replace |
Yeh, remove |
Humm, |
Probably because it's scanning files with only php 5.4 valid syntax. :/ |
This weird because i don't see any php 5.4 syntax in illuminate/contracts Edit: no i see php 5.4 array |
What is left to be done before this can be merged? Is it just figuring out how to make travis do it's thing? |
@hipsterjazzbo Unfortunately, the package |
Hmm. It's not really a matter of just getting travis to pass tests thought right? Like, if a dependency has 5.4 requirement, you won't be able to use it on 5.3 anyway? In that case, you either have to bump the PHP version requirement, or get rid of the dependency, right? |
I think we should just drop php 5.3 support totally. It's eol anyway. That would simplify this. // cc @philsturgeon |
Seems fair. I was going to keep dropping 5.3 for 1.0 but lets just knock the old Laravel adapter out and go with this new one.
Sorry to flip flop.
|
@philsturgeon Sounds like a plan. @maximebeaudoin Are you able to update your pull request, or should I send a new one? |
@GrahamCampbell I'll update mine in few minutes. |
Great. :) |
@@ -24,6 +24,7 @@ | |||
"phpunit/phpunit": "~4.0", | |||
"mockery/mockery": "~0.9", | |||
"illuminate/pagination": "~4.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to make this ~5.0.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or even remove it if the contracts repo does the job.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll remove "illuminate/pagination".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The suggests block probably need updating too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tbh, i think we should still "suggest" the pagination component itself.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, i'll keep it
efdaefd
to
c0cf402
Compare
I don't think we should rename the paginator class btw. |
@GrahamCampbell Yea, i'm wondering too because we have two different type of paginator into Laravel 5, but we can only support |
Yeah im ok with just supporting length aware. It sounds like the other one would fit in as a cursor better anyway |
So i keep the name |
IlluminatePaginatorAdapter is better imo. I see no reason to change it. The old one was length aware too. |
c0cf402
to
33fac71
Compare
Also bump php version from 5.3 to 5.4 and remove the old paginator adapter. Laravel 4 paginator is no longer supported.
33fac71
to
07272ca
Compare
I think this is it ! |
You need to bump the minor version in the branch alias too since this is a breaking change. |
Otherwise, 👍. |
IlluminatePaginatorAdapteror please |
Sorry my email client is f**ked up. |
Add the support for Laravel 5 paginator
I'll do that. Thank you! |
Related to the issue #150