Update http-mock to work with Guzzle 6

[lstrojny]

No description provided.

[alexeyshockov]

I can pick it on the next week.

[lstrojny]

Cool, thank you!

[alexeyshockov]

Is it about Guzzle 6 already? Now it makes sense to migrate directly to this version, I think. The issue was created long time ago, so I would like to be sure :)

[lstrojny]

Very true, let’s go to Guzzle 6.

[Ugoku]

Any news on this?

I got the following warning when installing http-mock "Package guzzle/guzzle is abandoned, you should avoid using it. Use guzzlehttp/guzzle instead."
Then after installing, it doesn't seem to work, as there is no hard Guzzle version requirement and things (function calls etc) change around a lot depending on which Guzzle version is installed...

[b1rdex]

OK guys, I think it's already time to face this issue and drop guzzle v3.
Can we discuss some roadmap/plan how these can be done?
We should split migration to new guzzle to simple and clear steps so it it would be easier to implement.

I would contribute if there will be clear vision of what and how needs to be done to migrate.

[lstrojny]

Thanks for everybody’s interest in this. It’s basically these steps:

• Update to a recent guzzle (replace guzzle/guzzle with guzzle/guzzlehttp)
• Fix the namespaces and method names and run the tests and see what breaks
• Fix stuff that breaks (most work will probably be in the UnifiedRequest class)

I myself have no time right now to work on this but I am happy to answer any questions in between if somebody else picks this up. While I don’t like the fact that we are depending on an abandoned library, http-mock is a testing only library and should never be used close to production anyway.

[b1rdex]

For all interested — take a look at https://github.com/mcustiel/phiremock
It has same approach, but already on guzzle 6+.