move "async Task<RestResponse<T>> ExecuteAsync<T>" from Extension to IRestClient

The extension-method

async Task<RestResponse<T>> ExecuteAsync<T>

Is the "natural" way to do a Request: everyting is TypeSave. But If you try to Mock IRestClient, you can only mock the Non-Typed Request-Reponse method.

In a Test-Scenario, we have to add the Serializers and use compute to Serialize & Deserialize, there is no full control on the response - the deserializers try to do the work - and an easy workaround with own serializer/deserialiser is not easy.

I had a long look at the sources, but using a custom Serializer did not worked out well. So I ended up with this Blog-Post unittest-with-restsharp

Yes, this works but is not intuitive.

Describe the solution you'd like

Having Task<RestResponse<T>> ExecuteAsync<T> in IRestClient would enable us to simple Mock the call. No additional Setup, No Serialization during the Test.

As far as I see, the ExtensionMethod can be moved to the RestClient-Implementation without breaking anything. All other ExtensionMethods will work, IRestClient-Implementation / Mocks will work.

You could move the method to the IRestClient Implementaion, extend the interface and remove the ExtensionMethod- without any side effects.

Describe alternatives you've considered

Considered? Mocking the Tests is complex. I considered to remove RestSharp - but my time is limited ;-) I did a complex initialization and hope my (future) colleagues will understand this in 2 years...

If I was unclear / any questions - may need some days for me to answer, but I'm here

Locate the ExecuteAsync extension method and the IRestClient interface and implementation in the repository. Review existing calls and tests around typed requests, then determine how the interface change affects mocking and existing extension-method consumers. Done means typed execution is available through IRestClient and the relevant tests cover mocked responses without serializer setup.