-
Notifications
You must be signed in to change notification settings - Fork 294
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
Merge current 1.x release into master #360
Conversation
* Extracted functions to static methods * Fixed typo in README
* Skipped a couple of tests on HHVM
Great news, thank you! It could use nightly for PHP 8.0 run |
c83f778
to
73e1954
Compare
…the lowercased keys for usage in in_array function.
Ok, onbly check that fails is the phpstan one. But not sure how much i should change for these errors.
|
…dle `gettype` very well and some cases were already handled in later in the stack.
61ebe24
to
202ba18
Compare
There, i've fixed the last phpstan errors, either by some extra checks or adding an ignore to lines where phpstan doesn't completely understand the code. |
So, just to confirm, there are no calls to the "functions" now, only to "static class methods", just like in the 1.x series. The next step would be to delete the functions entirely from the 2.x series. |
All function calls are removed and I even removed the functions.php itself and the tests. This was so I could verify there was no calls left. So yeah, fully merged and deprecated functions have been removed :)
Edit: Mobile typo's
|
Excellent. 👍 |
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.
this seems to be missing phpunit 9 update from #350
@Tobion valid point, will fix that. Seems there was some feedback also on the PR which was disregarded until 2.0, so that would mean some slight extra changes. |
I think it would be fine for that to be sorted in a follow-up PR. It's more important the other changes from 1.x make it into master than the test suite runs on PHPUnit 9. End users don't use the tests, but they do use what's in src. ;) |
Seems the tests were already merged, but forgot the change in the composer.json and phpunit.xml.dist. Everything is green. I did go though the feedback that was left on the phpunit PR and everything seems as promised :) |
I believe the changes requested in #360 (review) have been resolved, correct? @Tobion can you confirm that they've been addressed? Thanks! |
@Tobion hope you had a nice newyears, any chance you can review this any time soon? |
The HHVM specific code in this PR should be deleted. 2.x does not support HHVM, so the HHVM fixes in this PR should be taken out. |
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.
See my comment about removing HHVM.
Sure, i removed the 2 skips for the tests on HHVM. |
Would be nice to get this moving again :) |
I've looked at this and at first sight it looks good to me. Hard to compare the functions to the static calls though, but the tests are passing so 👍 |
Thank you Barry. The more people that review and tests this the more confident will the maintainer be to merge it. Your comment is much appreciated. |
@Nyholm and I have discussed this PR, and it includes unrelated changes and the merges to the utils classes seem to accidentally remove 2.x changes including return types. For this reason, I am going to start again here, so I can be sure everything is correct. Verifying everything in this PR is correct is as much work as me starting again here. I appreciate everyone's efforts here, and I hope this doesn't put anyone off future contributions. We just have to make sure the merge is good. :) |
I’m sure you done the best you possible can for this PR. But I cannot be 100% sure of the correctness. I also don’t know you as a contributors. This might be an issue with my need for control or trust issues, but if you where a person with poor intentions, this is a exactly the kind of PR one should hide bad code in. We will make sure a version of this PR is merged in the next few days. |
No problem at all. My main goal doing the work was to get this going and merged. I'm glad that is happening soon, even though its not my commit. Thanks for taking the time to get this up and running soon 😀
Outlook for Android<https://aka.ms/ghei36> downloaden
…________________________________
From: Tobias Nyholm <notifications@github.com>
Sent: Sunday, March 7, 2021 4:56:46 PM
To: guzzle/psr7 <psr7@noreply.github.com>
Cc: Björn Brala <bjorn@swis.nl>; Author <author@noreply.github.com>
Subject: Re: [guzzle/psr7] Merge current 1.x release into master (#360)
I’m sure you done the best you possible can for this PR. But I cannot be 100% sure of the correctness. I also don’t know you as a contributors.
This might be an issue with my need for control or trust issues, but if you where a person with poor intentions, this is a exactly the kind of PR one should hide bad code in.
We will make sure a version of this PR is merged in the next few days.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#360 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAZEN6R5EP6VRMGPYPDOIEDTCOO35ANCNFSM4UBC2BQA>.
|
If there is a new PR, can it be linked? As I understand this was blocking the availability of PSR-17 support in a stable release. Thanks! |
It is not. It has been multiple PRs. See the PRs creates in the past few days. Also note that master is already updated with code from 1.x. |
Reference for my comment: #327 (comment) |
I guess my question is, if this is not the way forward to have PSR-17 support in a stable release, then what is? We need some guidance since #327 has been stalled nearly a year and the last advice we were given here was to try to make the above merge happen. |
I've run into a blocker for us in issue #327 and thought I'd just go through the code and create a merge. This merges #345 and #347 so 2.x branch is up-to-date.
Hopefully this will unblock a 2.x release, since Drupal is waiting for this and out package swisnl/json-api-client.