-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
whitespace: update after moving to the analysis package
#4003
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
Conversation
1f3d6c8 to
9ab7274
Compare
9ab7274 to
e88f182
Compare
e88f182 to
c2ca764
Compare
| func notGoFmted() { | ||
| fmt.Println("Hello world") |
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.
Noticed here that we have the same situation as in #4003 (comment). Basically this results in the standalone linter and golangci-lint not fixing the same way, golangci-lint will leave the sapces before fmt whereas the linter itself will replace it with a tab.
I don't think there's anything we should do extra in this specific linter for this scenario (and also that's the same behaviour as before, we just didn't have a standalone linter) but yet another reason to try to integrate the suggested fixes with the golangci-lint fixer.
whitespace linter using the analysis packagewhitespace after moving to the analysis package
whitespace after moving to the analysis packageanalysis package
ldez
left a comment
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.
LGTM
The `whitespace` linter is rewritten to use `annalysis.Analyzer`. This PR will make use of the new code.
2850c9d to
57794a9
Compare
The
whitespacelinter is rewritten to useannalysis.Analyzer. This PR will make use of the new code.This is a draft PR until ultraware/whitespace#8 is merged and a new release has been made.