From bc8f8ab5d9de53a0e2a11c4fc96dd4839c1787f7 Mon Sep 17 00:00:00 2001 From: cbuto Date: Mon, 18 Jan 2021 16:28:20 -0500 Subject: [PATCH] Fix typo in style guide --- _posts/2020-11-09-golang-style-guide.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2020-11-09-golang-style-guide.adoc b/_posts/2020-11-09-golang-style-guide.adoc index e8adaacc2..61109ff3b 100644 --- a/_posts/2020-11-09-golang-style-guide.adoc +++ b/_posts/2020-11-09-golang-style-guide.adoc @@ -89,7 +89,7 @@ decide what to do with it, all the way up to the very entrypoint of the app (or You should almost NEVER use `panic`. Use custom error types. Create your own types that implement the `error` interface so that error messages are clear -and have well-defined types you can check against. For some examples of this, see e.g. the custom erros in the +and have well-defined types you can check against. For some examples of this, see e.g. the custom errors in the https://github.com/gruntwork-io/terratest/blob/master/modules/aws/errors.go[aws] package of `terratest`. Include stack traces. In most of our code, we have to wrap errors with