Skip to content
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

Replace our HTTP client abstraction by Guzzle #95

Closed
zimbatm opened this issue Apr 5, 2016 · 5 comments
Closed

Replace our HTTP client abstraction by Guzzle #95

zimbatm opened this issue Apr 5, 2016 · 5 comments

Comments

@zimbatm
Copy link
Contributor

zimbatm commented Apr 5, 2016

It's not worth hitting the same issues when Guzzle already did all the work.

Bonus point for creating a Pusher mock around Guzzle's

Fixes #87

@zimbatm zimbatm added this to the 3.0.0 release milestone Apr 5, 2016
@GrahamCampbell
Copy link
Contributor

👍

@kn100 kn100 removed this from the 3.0.0 release milestone Feb 27, 2018
@rvanlaak
Copy link

rvanlaak commented Apr 5, 2018

Note: the Guzzle client to be used should be passable via the constructor as optional argument, so everyone can keep using their Guzzle middleware.

@WillSewell
Copy link
Contributor

Could someone provide me with a list of benefits to end users of the library that using guzzle will bring?

@stale
Copy link

stale bot commented Mar 11, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you'd like this issue to stay open please leave a comment indicating how this issue is affecting you. Thank you.

@stale stale bot added the wontfix label Mar 11, 2021
@elverkilde
Copy link
Contributor

This was released in version 6.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants