-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
mispell in strings #522
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
Comments
jirfag
added a commit
that referenced
this issue
Jun 9, 2019
Treat Go source files as plain text files by misspell: it allows detecting issues in strings, variable names, etc. Also, it's the default mode of a standalone misspell tool. Also, implement richer and more stable auto-fix of misspell issues: now it can fix multiple issues in one line.
Hi, thank you for the report! The reason that golangci-lint doesn't find issues inside strings is that we run misspell in |
jirfag
added a commit
that referenced
this issue
Jun 9, 2019
Treat Go source files as plain text files by misspell: it allows detecting issues in strings, variable names, etc. Also, it's the default mode of a standalone misspell tool. Also, implement richer and more stable auto-fix of misspell issues: now it can fix multiple issues in one line.
jirfag
added a commit
that referenced
this issue
Jun 9, 2019
Treat Go source files as plain text files by misspell: it allows detecting issues in strings, variable names, etc. Also, it's the default mode of a standalone misspell tool. Also, implement richer and more stable auto-fix of misspell issues: now it can fix multiple issues in one line.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
embedded mispell did't find typo:
https://github.com/rekby/lets-proxy2/blob/4bbef7bf61ae15c3d4787f714e67a82397ef4a7b/internal/acme_client_manager/client_manager.go#L102
but standalone mispell did:
info:
golangci-lint has version 1.16.0 built from 97ea1cb on 2019-03-31T19:48:46Z
config:
golangci-lint run -v
The text was updated successfully, but these errors were encountered: