Skip to content

Fix a couple of issues in error handling documentation #243

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

Open
jjpinto wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Fix a couple of issues in error handling documentation #243

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1763de3
Fix a couple of issues in error handling documentation
jjpinto Dec 22, 2025
0a43982
Auto-update style.md
jjpinto Dec 22, 2025
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
4 changes: 2 additions & 2 deletions src/error-once.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ When a caller receives an error from a callee,
it can handle it in a variety of different ways
depending on what it knows about the error.

These include, but not are limited to:
These include, but are not limited to:

- if the callee contract defines specific errors,
matching the error with `errors.Is` or `errors.As`
Expand All @@ -30,7 +30,7 @@ For example, consider the following cases:
**Bad**: Log the error and return it

Callers further up the stack will likely take a similar action with the error.
Doing so causing a lot of noise in the application logs for little value.
Doing so causes a lot of noise in the application logs for little value.

</td><td>

Expand Down
4 changes: 2 additions & 2 deletions style.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1023,7 +1023,7 @@ When a caller receives an error from a callee,
it can handle it in a variety of different ways
depending on what it knows about the error.

These include, but not are limited to:
These include, but are not limited to:

- if the callee contract defines specific errors,
matching the error with `errors.Is` or `errors.As`
Expand All @@ -1049,7 +1049,7 @@ For example, consider the following cases:
**Bad**: Log the error and return it

Callers further up the stack will likely take a similar action with the error.
Doing so causing a lot of noise in the application logs for little value.
Doing so causes a lot of noise in the application logs for little value.

</td><td>

Expand Down