-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Adding new words #16
Comments
You are joining me somehow with the ticket I opened #15 |
Inside golangci-lint, you should use |
I wanted to contribute the new words to the project so all users can benefit. If you check the history of https://github.com/golangci/misspell/commits/master/words.go |
PS: |
if you are using misspell as a standalone thing, so maybe outside a Go tool, I would like you to look at the following projects:
And if you have a need to code something in golang, you can use Lines 70 to 76 in fd7b9c1
|
I had a look at some of these projects, but my experience so far is that they are too aggressive and often require an extensive configuration which would be a nightmare to maintain. I do like misspell because it does produce reasonably good results without any configuration. Yes, I will consider running misspell in |
Yes, but the commits that are not by the original author were backported of PRs from the original repo and IMO this was an error.
I will think about a CLI flag to define a path to a list of external words. |
I agree with you about cspell and vale. But you should take a look at |
Thanks, will check out The last time I tried codespell required a ton of configuration, even with it's |
I added a new option config.example.csv
$ misspell -dict config.example.csv ./temp
temp/temp.go:4:4: "acounts" is a misspelling of "accounts"
temp/temp.go:5:4: "canidate" is a misspelling of "candidate"
temp/temp.go:6:4: "comfirm" is a misspelling of "confirm"
temp/temp.go:7:4: "commiter" is a misspelling of "committer"
temp/temp.go:8:4: "converage" is a misspelling of "coverage"
temp/temp.go:9:4: "currrently" is a misspelling of "currently"
temp/temp.go:10:4: "delimeter" is a misspelling of "delimiter"
temp/temp.go:11:4: "differrent" is a misspelling of "different"
temp/temp.go:12:4: "exclusing" is a misspelling of "excluding"
temp/temp.go:13:4: "finshed" is a misspelling of "finished"
temp/temp.go:14:4: "formated" is a misspelling of "formatted"
temp/temp.go:15:4: "inderect" is a misspelling of "indirect"
temp/temp.go:16:4: "insuficient" is a misspelling of "insufficient"
temp/temp.go:17:4: "likly" is a misspelling of "likely"
temp/temp.go:18:4: "mergable" is a misspelling of "mergeable"
temp/temp.go:19:4: "overrided" is a misspelling of "overridden"
temp/temp.go:20:4: "priortized" is a misspelling of "prioritized"
temp/temp.go:21:4: "registeration" is a misspelling of "registration"
temp/temp.go:22:4: "reuqest" is a misspelling of "request"
temp/temp.go:23:4: "reviwer" is a misspelling of "reviewer"
temp/temp.go:24:4: "superceded" is a misspelling of "superseded"
temp/temp.go:25:4: "underlaying" is a misspelling of "underlying" |
Awesome, thanks! |
Great ! thanks @ldez |
I'd like to add new words, but words.go has a
DO NOT EDIT
comment, while it actually seems to have been edited in the past. Is it ok to edit?I would like to add these words found in the gitea codebase, hopefully all unambiguous:
The text was updated successfully, but these errors were encountered: