Repository navigation
PSR 17-18 compliance #1776
Description
Is your feature request related to a problem? Please describe.
It may cause transitivity issues when the project using / requiring this library also needs another version of Guzzle Http Client.
Describe the solution you'd like
It would be awesome to use PSR 17 HttpClientInterface instead of the concrete Guzzle Client class. Also, using RequestInterfaces, StreamInterfaces and their respective factories for payload would make sense IMHO.
Injecting the Client and Request factories (DIP) would be awesome but using discovery mechanism can also be something we can imagine.
More context
For instance, this library : https://packagist.org/packages/aporat/store-receipt-validator depends on Guzzle as well and we may have transitivity issues.
Reacted by Julien Herr, Deni, Menno Holtkamp, Stephan Vierkant, Richard Hagen, Fracsi, Richard van Velzen, Tac Tacelosky, Sylvain Martin Saint Léon, Victor Toulouse and 2 more
Activity
jdpedrie commentedon Jan 28, 2020
Thank you for the suggestion. We will consider it along with other planned changes!
tacman commentedon May 20, 2024
Hi, I see you just dropped support for Guzzle 6 and PHP 7.4 -- great! Perhaps that opens up an opportunity for using other http clients.
I'm a fan of the Symfony http client, because the requests are automatically logged in the debugger. Plus, it's already installed in my project, I'd prefer not to also download Guzzle.