-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
chore(deps): Bump golangci-lint from v1.62.0 to v1.62.2 #16250
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we should unexport the concrete encoders/decoders! They are helpful if you know the encoding!
@srebhan |
Yes but if I know I want the gzip decoder, why should I need to do the indirection? I don't see any value in this! Furthermore, the PR is about bumping the linter and you are changing code which is not related to the bump. So please leave the encoding as is. I see value in limiting the exported stuff for the plugins but not for the rest of the code-base... |
@srebhan Changed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we please move the change of the encoding/decoding things to a separate PR!? The title does not suggest those changes...
@srebhan
Usually, what we did was that if the bumped Here are excellent examples: |
@zak-pawel I'm a bit puzzled. We agreed on limiting the export stuff to the plugin directories only. So why does it warn for something in |
@srebhan Yes! You're right, I totally forgot about that.
Because the message format that we have excluded so far has been changed from |
Download PR build artifacts for linux_amd64.tar.gz, darwin_arm64.tar.gz, and windows_amd64.zip. 📦 Click here to get additional PR build artifactsArtifact URLs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @zak-pawel!
Summary
golangci-lint
bumped tov1.62.2
revive:max-public-structs
reenabled (following issue has been fixed and released inrevive
andgolangci-lint
: Themax-public-structs
rule starts finding many false positives in version1.5.0
mgechev/revive#1103New findings addressed:
Checklist