refactor: use std errors following errorlint rules - #3272
Open
mmorel-35 wants to merge 1 commit into
Open
Conversation
Signed-off-by: Matthieu MOREL <matthieu.morel35@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
- What I did
use standard
errorsinstead ofgithub.com/pkg/errorsalong with activation oferrorlintlinter anderrorf,unnecessary-formatanduse-errors-newrules fromrevive- How I did it
Replace
github.com/pkg/errors.Wrap[f](err, "...")withfmt.Errorf("...: %w", err)same logic goes for error comparisons and type checking. Everything was done manually with only the help of golangci-lint- How to test it
- Description for the changelog
Fixes #3203