-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
✨ (go/v4): Add new makefile target to check and validate the linter config #4425
Changes from all commits
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 |
---|---|---|
|
@@ -18,7 +18,11 @@ issues: | |
|
||
linters-settings: | ||
govet: | ||
enable=fieldalignment: true | ||
enable-all: true | ||
disable: | ||
- fieldalignment | ||
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. @camilamacedo86 as configuration was wrong, it was not enforcing I disabled it because there are several files affected I suggest we merge this one, and fix the linter errors in follow up |
||
- nilness | ||
- shadow | ||
revive: | ||
rules: | ||
# The following rules are recommended https://github.com/mgechev/revive#recommended-configuration | ||
|
@@ -28,7 +32,7 @@ linters-settings: | |
- name: dot-imports | ||
arguments: | ||
# dot import should be ONLY allowed for ginkgo testing packages | ||
allowedPackages: | ||
- allowedPackages: | ||
- "github.com/onsi/ginkgo/v2" | ||
- "github.com/onsi/gomega" | ||
- name: error-return | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -82,6 +82,10 @@ test-e2e: manifests generate fmt vet ## Run the e2e tests. Expected an isolated | |
} | ||
go test ./test/e2e/ -v -ginkgo.v | ||
|
||
.PHONY: lint-config | ||
lint-config: golangci-lint ## Verify golangci-lint linter configuration | ||
$(GOLANGCI_LINT) config verify | ||
|
||
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. We change things for end users, so as it is an addition, we should use ✨ since it should be highlighted in the release notes. |
||
.PHONY: lint | ||
lint: golangci-lint ## Run golangci-lint linter | ||
$(GOLANGCI_LINT) run | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -78,6 +78,10 @@ test-e2e: manifests generate fmt vet ## Run the e2e tests. Expected an isolated | |
} | ||
go test ./test/e2e/ -v -ginkgo.v | ||
|
||
.PHONY: lint-config | ||
lint-config: golangci-lint ## Verify golangci-lint linter configuration | ||
$(GOLANGCI_LINT) config verify | ||
|
||
.PHONY: lint | ||
lint: golangci-lint ## Run golangci-lint linter | ||
$(GOLANGCI_LINT) run | ||
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. We have an error in the samples (main.go) that we need to ignore But if you have a better idea please feel free to try out |
||
|
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.
@mateusoliveira43 this change seems unrelated to the scope right?
Seems that if we change it, then we will start to fail where we did not before
Is that falling under the new target to validate the configuration?
Why do we need to do this change?
If we need to make this change, we need to fix the issues as well
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.
So, looking CI errors, I think the only complain is indeed
fieldalignment
errors (I do not know yet whylint-sample
failed)should I disable it?
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.
We should not disabled the lint-simple
The lint sample has the purpose of lint the test samples and ensuring that the code that we generate with the tool passes the checks.
Why we need to change
enable=fieldalignment: true
can we please revert that it does not seems part of the scope then, if you wish change it we can do in a follow up where the issues are fixed and we explain why one option should be used instead of anotherThere 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.
Moreover, we need to have a new target for the Makefile that we use for Kubebuilder as well.
It can be here, and we do all by once, for our samples and tooling or can be in a follow up PR
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.
oh no, I mean disable
fieldalignment
ruleIf you check lint job logs, all errors were related to this rule
I made the change because
golangci-lint config verify
complained about this configurationbut we can change this part of project Makefile in a separate PR
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.
undid changes to configuration, just added new command to project Makefile, without calling it in CI
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.
Should it not fail in the CI if the lint raises errors and we revert the change?