A linter that checks for duplicate words in the source code (usually miswritten)
Examples in real code and related issues can be viewed in dupword#3
- Repeated words appear on two adjacent lines commit
--- a/src/cmd/compile/internal/ssa/schedule.go
+++ b/src/cmd/compile/internal/ssa/schedule.go
@@ -179,7 +179,7 @@ func schedule(f *Func) {
// scored CarryChainTail (and prove w is not a tail).
score[w.ID] = ScoreFlags
}
- // Verify v has not been scored. If v has not been visited, v may be the
+ // Verify v has not been scored. If v has not been visited, v may be
// the final (tail) operation in a carry chain. If v is not, v will be
// rescored above when v's carry-using op is scored. When scoring is done,
// only tail operations will retain the CarryChainTail score.- Repeated words appearing on the same line commit
--- a/src/net/http/cookiejar/jar.go
+++ b/src/net/http/cookiejar/jar.go
@@ -465,7 +465,7 @@ func (j *Jar) domainAndType(host, domain string) (string, bool, error) {
// dot in the domain-attribute before processing the cookie.
//
// Most browsers don't do that for IP addresses, only curl
- // version 7.54) and and IE (version 11) do not reject a
+ // version 7.54) and IE (version 11) do not reject a
// Set-Cookie: a=1; domain=.127.0.0.1
// This leading dot is optional and serves only as hint for
// humans to indicate that a cookie with "domain=.bbc.co.uk"go install github.com/Abirdcfly/dupword/cmd/dupword@latestOr install the main branch (including the last commit) with:
go install github.com/Abirdcfly/dupword/cmd/dupword@mainRun with default settings(include test file):
But note that not all repeated words are wrong see dupword#4 for real code example.
$ dupword ./...
/Users/xxx/go/src/dupword/dupword_test.go:88:10: Duplicate words (the) found
exit status 3Skip detection test file(*_test.go):
$ dupword -test=false ./...$ dupword -fix ./...All options:
$ dupword --help
dupword: checks for duplicate words in the source code (usually miswritten)
Usage: dupword [-flag] [package]
This analyzer checks miswritten duplicate words in comments or package doc or string declaration
Flags:
-V print version and exit
-all
no effect (deprecated)
-c int
display offending line with this many lines of context (default -1)
-cpuprofile string
write CPU profile to this file
-debug string
debug flags, any subset of "fpstv"
-fix
apply all suggested fixes
-flags
print analyzer flags in JSON
-ignore value
ignore words
-json
emit JSON output
-keyword value
keywords for detecting duplicate words
-memprofile string
write memory profile to this file
-source
no effect (deprecated)
-tags string
no effect (deprecated)
-test
indicates whether test files should be analyzed, too (default true)
-trace string
write trace log to this file
-v no effect (deprecated)use --keyword=the,and,a and -fix together. I think that specifying only commonly repeated prepositions can effectively avoid false positives.
see dupword#4 for real code example.
$ dupword --keyword=the,and,a -fix ./...- add this linter to golangci-lint
- rewrite the detection logic to make it more efficient
- Only for
*.gofile.But some miswritten occurs in*.mdor*.jsonfile.(example: kubernetes), In this case, my advice is to use rg to do the lookup and replace manually. - When use
-fix, also runninggo fmtin the dark.(This logic is determined upstream, the project does not have this part of the code.)
MIT