I have updated the description. If possible I would like some comments :)

I find it weird that we encourage people to use standards like PSR-17, but we also suggest using ourRequestOptions.

What's the point in using PSR-17 then? People will hardly use an entirely different PSR-7/PSR-17 package with our options.

People will hardly use an entirely different PSR-7/PSR-17 package with our options.

I will revert this.. Most probably ppl will not use PSR-7/PSR-17/PSR-18 if they have to build a request in a verbose way when they can simply use$client->get('uri', ['query' => ['key' => 'value']]);

Extractingapply_options makes the pain less.

FYI about a year ago I've found it very difficult to get the team working with PSR clientes because they are too verbose, so I ended up creating a wrapperhttps://gist.github.com/gnumoksha/b35d97613dd729315d3dc1ba0449544a

so I ended up creating a wrapperhttps://gist.github.com/gnumoksha/b35d97613dd729315d3dc1ba0449544a

Nice. :P That code is an example of where the new ClientTrait could be used. ;)

https://github.com/guzzle/guzzle/blob/master/src/ClientTrait.php

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 2 weeks if no further activity occurs. Thank you for your contributions.

#3135 has now been merged, replacing#1890.

Will try to re-initiate this.

Thanks@GrahamCampbell .. Please give me an ETA of 5 days.. if you don't hear from me please proceed with any other implementation