-
-
Notifications
You must be signed in to change notification settings - Fork 710
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
pre-commit should have at least one spell-checker #302
Comments
Why not just use GNU Edit: There's also |
I would prefer a tool that can easily be installed by pre-commit at runtime on most platforms, which means: python, nodejs or ruby based. Other approaches would make harder to assure succesfuly precommit installation. Currently I am using cpell on few projects but not as hook yet. PS. We do not want to add system package requirements to pre-commit, for portability reasons. I really like the fact that now it works well on almost any platform. |
I think we tick those boxes, and someone added a hook, although I see it's not listed and I get the feeling there's a step missing to run it from the pre-commit config: codespell-project/codespell#1117 |
I used cspell on a couple of projects and it proved to be a real PITA, issues with installation and also usage. I am going to five codespell a chance and see how it goes. Lets not close the ticket yet as there is a real need to spell code and also commit messages. |
Sadly only some kind of magic machine learning algorithm might catch those sort of issues. 😃 |
ah I'll add it to the website -- thanks @peternewman (that's handled through https://github.com/pre-commit/pre-commit.github.io) |
Thanks @asottile, yeah I'd seen that site, I was assuming people would need to do a bit more work to codespell, but I see the system essentially just calls the existing library/executable by default. |
yep! all that's needed is the little metadata file and |
Spellchecking in commit message, comments and source code is more than a trivial issue as git history cannot be realistically be changed and because spelling errors slipping into API do become the "norm" and they are very hard to fix later due to the need to avoid breaking the API.
I have not special speller in mind but I wanted to share with you experience about two of them:
Update: streetsidesoftware/cspell#56 ticket would track adding the hook definition on cspell.
The text was updated successfully, but these errors were encountered: