@nitishm Just asking: since the generated client here accepts an HTTPClient, the retry mechanisms or any other advanced stuff like oauth2 should already be possible. What would make sense is provide maybe an extension to the Readme how one can create some cool HTTPclients and inject them in the generates client here. But maybe I am misunderstanding something.

@nitishm Just asking: since the generated client here accepts an HTTPClient, the retry mechanisms or any other advanced stuff like oauth2 should already be possible. What would make sense is provide maybe an extension to the Readme how one can create some cool HTTP clientsΩ and inject them in the generates client here. But maybe I am misunderstanding something.

The standard HTTP client is pretty good but there are cases where you might want to wrap it with some extra functionality (think decorator pattern).
Let's say we want the client to automatically log before and after a POST command. The wrapper struct would allow us to add the functionality by implementing the interface, but under the hood continue to use the standard go HTTP library
For instance, the wrapping struct would look like below,

type Wrapper struct {
    logger logrus.Logrus
    client *http.Client
}

In my case, I am looking to add some retry options to the HTTP client using different backoff strategies. Unfortunately, the standard HTTP client library does not provide retry capabilities, and due to the generated code using oapi-codegen client, I cannot modify it to include retry capability.

@weitzj Hope that makes sense. Let me know if you think there is a better alternative.

Hey, How does this compare to #85 ?

Seems like this was already done in #85 and can be closed.