HttpTransporter object to return error instead of throwing it. about client HOT 4 CLOSED

Yes please, upvoting for that! Better error handling would be much appreciated!

from client.

Just to be clear, I have already done the needed changes in the codes on my local machine and the above test passes nicely.
I have achieved this with minimum changes necessary, though one may suggest bigger and more fundamental changes to the structure of the whole component, I found it not needed at presence.
Plus, I stopped using this component in favor of using the native Symfony Httpclient instead of this nice component, due to its entangled use of Guzzle.

from client.

Hi @ali-m2020

Thank you for input. But I can't see what the benefit of not throwing an exception should be, because in my opinion all the 4 things you mentioned should be possible with the current implementation.

Furthermore, not throwing an exception and returning a valid response object with a new "error" attribute would require an additional check after every request to ensure the returned response has no error.
With the current implementation this check is not required as the developer can be sure, that every response received is valid and no error has occurred.

If I misunderstand your request or there is a concrete error which you are not able to handle properly, please let us know.

@kamilbaranek Why did you upvote for this feature? What change would you expect?

from client.

closed due to inactivity

from client.