-
Notifications
You must be signed in to change notification settings - Fork 624
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: fix linter warnings #3311
Changes from all commits
fe8a679
4444563
c48c02c
2438e95
2fd14d3
f4bcec4
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -22,5 +22,5 @@ jobs: | |
- name: golangci-lint | ||
uses: golangci/[email protected] | ||
with: | ||
version: latest | ||
version: v1.52.0 | ||
args: --timeout 5m |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -107,11 +107,7 @@ func SetupICAPath(path *ibctesting.Path, owner string) error { | |
return err | ||
} | ||
|
||
if err := path.EndpointB.ChanOpenConfirm(); err != nil { | ||
return err | ||
} | ||
|
||
return nil | ||
return path.EndpointB.ChanOpenConfirm() | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. so an update to the linter started to trigger all these? Happy to honour the linter here, just playing devils advocate. I think sometimes linters can be overly aggressive. We can always tweak the config later I guess. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It might be beneficial to add There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, looks like golangci-lint was bumped to v1.52 and hell broke loose... I had second thoughts when I was changing these as well, but thought the improvement was justified. I don't think the link would have complained if there was some extra logic inside the if statement. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Yes, thank you for the suggestion, @DimitrisJim, we do use those directives in some places of the codebase. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I agree with @damiannolan, I think it'd be nice to be able to turn off this specific linting check. I don't see a lot of value in enforcing it, but I do see value in not enforcing it |
||
} | ||
|
||
func (suite *InterchainAccountsTestSuite) TestOnChanOpenInit() { | ||
|
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.
This linter rule complains when a named argument in a functions is not used