Generator error: Client responses with body about oapi-codegen HOT 2 CLOSED

If I understand this issue correctly, this is actually by design.

The client and server interfaces are not identical, since we still require some work to be done by the caller.

For the server interface, you are expected to put the response body on the context in the handler function. The response handling is out of our hands. Your handler returns an error if there was an error in the processing of the response, not if there's an error returned via HTTP. The semantics are the same as returning error from an echo handler.

For the client interface, we generate the request for you, and hand back an unprocessed http.Response for you to interpret. This is where the asymmetry comes from.

from oapi-codegen.

Ah you're right! Sorry I didn't describe the problem I was attempting to solve better.

In the project I was working on I was purely using this as a client and was ignoring the server aspect. I was experimenting with creating additional generators with implementations for interpreting thehttp.Response by parsing it as as yaml or json into model representations. I got carried away and confused with code reuse

from oapi-codegen.