Custom Global Default Config about guzzle HOT 2 CLOSED

Thanks for getting in touch. My feeling is that this static global state is a bad practice, and I'm not particularly interested in perusing this in the library core. Frameworks like Laravel have a way of providing syntax that looks like that, but is actually not that, which could be a way to achive what you want with configuring defaults, or making a factory class. I indeed have such a package https://github.com/grahamCampbell/guzzle-factory. ;)

from guzzle.

I agree the pointers you give work fine for building things moving forward.

I don't think they work as well when you're trying to update things for a large existing code base with disparate usage of Guzzle clients. Or am I missing something?

from guzzle.