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

Fix new lints #86

Merged
merged 3 commits into from
Aug 3, 2023
Merged

Fix new lints #86

merged 3 commits into from
Aug 3, 2023

Conversation

SuperSandro2000
Copy link
Member

No description provided.

These type-safe interfaces around errors.As() and errors.Is() should
make it easier to resolve the errorlint warnings without making the code
uglier.
Copy link
Contributor

@majewsky majewsky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@SuperSandro2000 I added two commits that I would like for you to counter-review. The first adds more type-safe interfaces around errors.As, as we discussed over the lunch break. The second showcases a way that many of the places you marked as nolint can be rewritten to take advantage of errors.Is() without compromising the existing structure too much. Please take this change under consideration for the application repos, too.

@SuperSandro2000 SuperSandro2000 merged commit d2170ec into master Aug 3, 2023
6 checks passed
@SuperSandro2000 SuperSandro2000 deleted the lints branch August 3, 2023 11:54
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.

None yet

2 participants