requests
HTTP requests for Gophers (by earthboundkid)
errors
Simple error handling primitives (by pkg)
requests | errors | |
---|---|---|
25 | 30 | |
1,401 | 7,511 | |
- | - | |
6.7 | 0.2 | |
23 days ago | over 2 years ago | |
Go | Go | |
MIT License | BSD 2-clause "Simplified" License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
requests
Posts with mentions or reviews of requests.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-12-13.
- I wrote my own Go HTTP client
- requests v0.23.4 with XML support
-
How use gorilla/http for requests
Here is a good HTTP client library that is still under maintenance: https://github.com/carlmjohnson/requests
-
The Go libraries that never failed us: 22 libraries you need to know
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.
-
Too many returns?
Yeah, tons of boilerplate. See https://blog.carlmjohnson.net/post/2021/requests-golang-http-client/
-
How I write offline API tests in Go
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.
- Libraries you use most of your projects?
-
json response data from curl tool is different than http.Get method.
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.
-
How GoLang Generics Empower Concise API: HTML Table Extraction Case Study
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.
-
go-vcr v3 has been released
VCR is a great project, and because it uses the standard Go http.RoundTripper interface, you can use it with other projects!
errors
Posts with mentions or reviews of errors.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-11-29.
-
Show HN: Error return traces for Go, inspired by Zig
Can you explain why we should this over https://github.com/pkg/errors?
-
Cant wait for less verbose error handling
The pkg/errors package offers some nice add-ons for easier error handling. Too bad it was put into maintenance mode pending whatever changes/improvements are coming in Go 2.
- Error handling and serializing
-
isse for go path in neovim
I can't figure out the issue so here for some help, I am using `neovim/nvim-lspconfig` my `gopls` doesn't recognise external paths such as `github.com/pkg/errors` , it throws error`could not import github.com/pkg/errors (cannot find package "github.com/pkg/errors" in any of /usr/local/go/src/github.com/pkg/errors (from $GOROOT) /Users/ra compiler (BrokenImport)\`
-
What am I supposed to be doing with errors?
Also - there are some error handling utils that allow you to wrap errors before passing: https://github.com/pkg/errors
-
Go error handling is not verbose but the error handling itself.
Should've been something like errors.Newf("failed to foofoo %s", foo) instead and preferably never invent %w but have some controlled way to wrap like errors.Wrapf(err, "failed to foofoo %s", foo) that was in ye olde github.com/pkg/errors.
-
How to wrap the error best?
Prefer using errors.Wrap and errors.Wrapf from https://github.com/pkg/errors . It's frozen because they don't want to add features, waiting for a re-write of error handling in Go2.
- mdobak/go-xerrors: Yet another error handling library.
-
Getting at the type of error after it has been wrapped with errors.Wrap
Im using zerolog and in order to get the stack trace for my error I have to wrap my error in errors.Wrap from "github.com/pkg/errors".
-
When ia a good time to panic?
And for "real programs" you can use https://github.com/pkg/errors (if you want stack traces)
What are some alternatives?
When comparing requests and errors you can also consider the following projects:
httpx - Reliable HTTP for GoLang
zerolog - Zero Allocation JSON Logger
go-http-client - An enhanced and lightweight http client for Golang
autoflags - Populate go command line app flags from config struct
req - Simple Go HTTP client with Black Magic
go-multierror - A Go (golang) package for representing a list of errors as a single error.
heimdall - An enhanced HTTP client for Go
logrus - Structured, pluggable logging for Go.
httpretry - Enriches the standard go http client with retry functionality.
bitio - Optimized bit-level Reader and Writer for Go.
packet - :package: Send network packets over a TCP or UDP connection.
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library