-
Notifications
You must be signed in to change notification settings - Fork 30
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: Bump golangci-lint make and action #1346
Conversation
@@ -114,7 +114,7 @@ func (r *KymaReconciler) Reconcile(ctx context.Context, req ctrl.Request) (ctrl. | |||
status.InitConditions(kyma, r.SyncKymaEnabled(kyma), r.WatcherEnabled(kyma)) | |||
|
|||
if kyma.SkipReconciliation() { | |||
logger.V(log.DebugLevel).Info(fmt.Sprintf("skipping reconciliation for Kyma: %s", kyma.Name)) | |||
logger.V(log.DebugLevel).Info("skipping reconciliation for Kyma: " + kyma.Name) |
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.
It's surprising that the linter doesn't enforce consistent usage of the +
operator. E.g., here we surround it with blanks whereas in the change in cmd/main.go
we don't have blanks. Changing that in either way leads to linting errors 🤷🏻♂️
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 just checked out of curiosity. It depends on the number of arguments passed to the func. If it is one arg only, it enforces whitespace x + y
, if it is more than one arg it enforces no whitespacex+y
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.
Curious, I know. 😄
Description
Changes proposed in this pull request:
Related issue(s)