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
Allow httplug 2.0 #802
Allow httplug 2.0 #802
Conversation
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.
Yes, it is very possible.
Difference between version 1 and 2 of php-http/httplug is just PHP7 return types.
Ok bumping the supported php version to 7.1 (currently the oldest supported version) would kinda solve this. But the failures in travis are related about return typehints, but adding them here (and matching those of httplug) is a BC break in our lib as users could extend these classes/methods. Or am I seeing things wrong here? |
Not needed if we still support version 1.0 of httplug. |
@Nyholm but without bumping php we can't support httplug 2.0. So I guess the only way to do it, is to bump the major version and switch to httplug v2? |
06efa6d
to
93a2d27
Compare
Ok, this looks promising! @Nyholm I've found your PR for the mailgun api lib and so I learned that the I will take a look next time to get these tests passing again |
a52f146
to
0fae913
Compare
Implementation is done and all tests are green now, but as I suspected the BC check fails now. So I guess really the only way to do it is bump the httplug requirement to v2 in the next major release? |
0fae913
to
88cb0f6
Compare
88cb0f6
to
206078e
Compare
Sorry for being slow coming back to this. The BC warnings you see is actually fine =) You get a bunch new from our The other "BC warnings" comes from our plugins. They use the "version bridge" to automatically adapt if you installed HTTPlug v1 or v2. |
Thank you @acrobat for the work you put in to this. |
A pr to try/test if we can support both v1 and v2 of httplug. Currently there are still errors regarding typehint incompatibilities, so still a WIP to get things up and running
/cc @Nyholm is it actually possible to support both versions?