-
Notifications
You must be signed in to change notification settings - Fork 6
Upgrade to react/http instead of react/http-client which is deprecated. #42
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
Since the react/http-client library is now deprecated we need to move forward with the ecosystem. We also use the new Psr7 factories from the nyholm/psr7 package.
e5e2d74
to
7cc09dd
Compare
thanks! this seems good to me. can you maybe adjust the style-ci configuration to the newest symfony ruleset (remove the explicit rule that is now in the symfony ruleset)? should we bump this to a new major version? it could be unexpected to have the underlying react library change completely when upgrading. |
Ok I take a look at the style-ci configuration. For sure it must be a new major version for this adapter. If some users have tweaked the reactphp behaviour, their code will not work anymore. |
da751e3
to
b80ffda
Compare
Also upgrade all the test suite to match the new behaviour.
b80ffda
to
dcfab46
Compare
please change composer.json where it says
to say 3.x-dev we did not release the last commit to master as 2.4 yet - it was the switch to httplug 2. however, i think the correct way is to get this merged as well, rather than a release 2.4 for the switch to httplug 2. do you agree? |
dcfab46
to
c8d7056
Compare
Ok, I've just updated the composer.json file… Maybe we can release the two different tags. I think that users can have advantage to use the httplug 2 no ? Maybe we'll have to path the v2 branch at some time… It'll require a tiny changelog update for the v2.4.0 branch to be published. |
my thinking was that we could merge this and release as 3.0.0 immediately. i would not be aware of other BC breaking things we need to do. that would keep the number of different versions a bit lower. and it might be problematic for some when we switch to httplug 2 in a minor version... |
You're absolutely right 😄. I close the #44 and merge this one. Then I'll commit the changelog update on master for the v3.0.0 release 😉. |
hooray, thanks! |
What's in this PR?
The adapter now rely on
react/http
instead ofreact/http-client
. TheClient
external behaviour hasn't changed but all the inner logic is now rewritten.Because
react/http
hasn't a compatible signature withreact/http-client
this is a BC Break and will require a new major version of the adapter.Why?
react/http-client
is now deprecated so we must move with the ecosystem.Checklist