Skip to content
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.

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

Add a linter for detecting fmt.Errorf w/ %w #1952

Merged
merged 1 commit into from
May 9, 2023

Conversation

timraymond
Copy link
Member

It was decided by the team that we prefer errors.Wrap over the standard library error wrapping mechanism because pkg/errors provides a more consistent experience by default. This adds a simple linter to detect usages of the standard library error wrapping.

It was decided by the team that we prefer errors.Wrap over the standard
library error wrapping mechanism because pkg/errors provides a more
consistent experience by default. This adds a simple linter to detect
usages of the standard library error wrapping.
@timraymond timraymond requested review from rbtr, matmerr and a team as code owners May 9, 2023 17:12
@rbtr rbtr merged commit 35b8cc3 into Azure:master May 9, 2023
@timraymond timraymond deleted the error-linter branch June 28, 2023 15:19
rbtr pushed a commit that referenced this pull request Sep 8, 2023
It was decided by the team that we prefer errors.Wrap over the standard
library error wrapping mechanism because pkg/errors provides a more
consistent experience by default. This adds a simple linter to detect
usages of the standard library error wrapping.
jpayne3506 pushed a commit that referenced this pull request Sep 11, 2023
It was decided by the team that we prefer errors.Wrap over the standard
library error wrapping mechanism because pkg/errors provides a more
consistent experience by default. This adds a simple linter to detect
usages of the standard library error wrapping.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants