guide
guide copied to clipboard
uber-go
The Uber Go Style Guide.
Creating this to track adding a general guideline around logging-vs-returning errors, and doing only one of the two at any error handling site to avoid double logging.
While I'm sure it might add an extra step, another thing to do for PRs, I think having "Releases" would help people that are not actively participating, but want to...
Using `var _ http.Handler = (*Handler)(nil)` is a great idea to make sure that `Handler` implements `http.Handler` properly. What if both the interface and the struct using generic? For example:...
I would love to help translating this Guide to German. Please let me know the way forward.
At section with [Errors Types](https://github.com/search?q=org%3Auber%20github.com%2Fpkg%2Ferrors&type=code) mentioned only about standart go library errors, but [github.com/pkg/errors](https://github.com/pkg/errors) is popular as well, we can find a lot of references of it at Uber open...
I feel we can remove the nesting from the code present in "Error Types" section under "Error" Category in Style.md file From - ```go // package foo var ErrCouldNotOpen =...
Hello, I am researching different scenarios for propagating errors through Golang API, also different way of encapsulating the errors for the whole API. I will give some examples and I...
> **Note** All credit goes to @abhinav This PR adds suggestions on formatting strings using `%q` over `%s`. Source: https://abhinavg.net/2021/12/29/fmt-errof-q/ by @abhinav Fixes #185
> **Note** All credit goes to @abhinav I learned this from one of @abhinav's amazing talks, and thought we could probably add this practice to this doc. Whenever formatting messages...
The exact wording is TBD - this is to start a discussion. My personal preference is to use table-test all the time, and would obviously would like it to be...
