Skip to content

Fix typo in style guide #395

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 19, 2021
Merged

Fix typo in style guide #395

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion _posts/2020-11-09-golang-style-guide.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down