go-wecom VS requests

requests is not declarative for me, this is what I mean declarative https://github.com/wenerme/go-wecom/blob/main/wecom/client_agent.go , requests is more like https://github.com/parnurzeal/gorequest , just chain everything. context.Context is not required, but just can be passed by.

Here is a good HTTP client library that is still under maintenance: https://github.com/carlmjohnson/requests

https://blog.carlmjohnson.net/post/2021/requests-golang-http-client/ talks about why that’s the API. To be honest, I think a lot of people have an irrational fear of mutability. If you want to make a clone, use .Clone(). If not then don’t. But if you don’t like mutability, you’re going to dislike using the Go standard library, which uses mutable package variables all over the place.

Yeah, tons of boilerplate. See https://blog.carlmjohnson.net/post/2021/requests-golang-http-client/

Yeah, I made a simple response recorder inspired by VCR. VCR is a little more complex than I need but the basic approach is great.

The native Go HTTP library is very capable, but it is extremely verbose. At the risk of introducing more complexity, I suggest using https://github.com/carlmjohnson/requests just so you don’t have to deal with checking all the errors and making the status code is correct.

What the other commenter said but also read this: https://blog.carlmjohnson.net/post/2021/requests-golang-http-client/ It talks about the need for clients and contexts throughout.

VCR is a great project, and because it uses the standard Go http.RoundTripper interface, you can use it with other projects!