-
Notifications
You must be signed in to change notification settings - Fork 32
Add support for HTTPlug 2.0 #24
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
Conversation
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here (e.g. What to do if you already signed the CLAIndividual signers
Corporate signers
|
Codecov Report
@@ Coverage Diff @@
## 2.x #24 +/- ##
=========================================
Coverage 86.35% 86.35%
Complexity 627 627
=========================================
Files 92 92
Lines 1370 1370
=========================================
Hits 1183 1183
Misses 187 187 Continue to review full report at Codecov.
|
Wow, HTTPlug 2.0 has just released. That was quick... :) Thanks @GeorgosXL for your PR. Please sign the CLA and submit a link to a Travis build that proof your changes does not break any tests even when the online client is being used. (PR tests use mock responses, they do not call the Apigee Edge API.) Expected link is something like this: https://travis-ci.org/mxr576/apigee-client-php/builds/448781277 |
Related: php-http/client-common#114 So we should not hurry with this merge of this PR because there are plenty php-http components that version needs to be bumped and for that they need to be compatible with HttpPlug 2.0 (precisely the finalized PSR-18). |
Besides the CLA, I think it would be fair to just do a manual review for a small PR like this one. Of course the dependency that changed should be reviewed as well. |
@Jaesin You may think a simple version bump is a "small" change, but we have even seen recently that a simple minor version (reminder, this is a major version update) about in PHP API client's dependencies can break the library. See #20. I though it is going to be a simple update but luckily our online test suite that Travis executes revealed that if we would update to the latest major version from the php-client/client-common the PHP API client would stop working. |
could not be installed with apigee/apigee-client-php 2.0.0-alpha6 version. The upgrade to the 2.0 version should eliminate this problem: apigee/apigee-client-php#24
Client common library's 2.0 version is still in progress: php-http/client-common#115 |
It seems we can not support 2.x version from php-http packages without releasing a new major version from this library. I am closing this PR and opening an issue where I try to collect all info that I have regarding this. |
No description provided.