Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Like a lot of other people I'm using other libraries that require Guzzle 5 so I haven't been able to upgrade to Guzzle 6. Now the opportunity has come to upgrade all the libraries I use to the latest Guzzle version, but I didn't want to break backwards compatibility and force people to upgrade if they can't. The best way to go about this is to use an abstraction library, like HTTPlug which will allow users to choose their own version of Guzzle.
I've tried to keep upgrading as simple as possible. For most users it will work out of the box but some changes are unavoidable. They are:
event.before
,event.after
andevent.error
now take different parameters rather than Guzzle Event objects.@sesser perhaps you want to create a new major version for this as a result of the non-BC breaks above?