-
Notifications
You must be signed in to change notification settings - Fork 471
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
Add note about not being a general spell checking tool. #1535
Conversation
Out of interest @tir38 what was missing to make it a general spell checking tool? What makes you think it isn't one? |
I tried to test this by just barfing rando text into a file (e.g.
|
It looks for common spelling mistakes rather than membership in a complete dictionary. Maybe it can be rephrased to take this into account? |
@larsoner yep, that was what I hoped to accomplish by updating the README |
Co-authored-by: Eric Larson <[email protected]>
@@ -3,6 +3,9 @@ codespell | |||
|
|||
Fix common misspellings in text files. It's designed primarily for checking | |||
misspelled words in source code, but it can be used with other files as well. | |||
It does not check for word membership in a complete dictionary, but instead | |||
looks for a set of common misspellings. Therefore it might catch errors like | |||
"adn", but it will not catch "adnasdfasdf". | |||
|
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.
Derp. Talk about circular dependency. Using Codespell to check readme of repo finds spelling error, which only exists to show example of spelling error. Not sure if I should fix this.
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.
Well at least we know it's working @tir38 ! Joking apart we could either ignore the line or add the specific typo to an allowed list (although if we do the latter it would be better if it was a more obscure word/less likely typo, but perhaps that defeats the point of the example; abandonned
is our goto typo, but it's not as obvious as the example one).
@larsoner Travis didn't catch this as it's only checking the module source stuff, not the surrounding files:
codespell --skip="codespell_lib/tests/test_basic.py,codespell_lib/data/*" codespell_lib/
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.
Feel free to add it to the checks
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.
Done in #1596
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.
See #1535 (comment) for more detail of fixes.
Sorry this slipped by the wayside @tir38 . I think it would still make sense to get it in. To avoid the error it's now trapping (due to #1596), we'll need to skip it, the safest way is probably adding an exclude file into |
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.
Sorry this slipped by the wayside @tir38 . I think it would still make sense to get it in, do you want to have a go. I think the following changes should do the trick.
@@ -3,6 +3,9 @@ codespell | |||
|
|||
Fix common misspellings in text files. It's designed primarily for checking | |||
misspelled words in source code, but it can be used with other files as well. | |||
It does not check for word membership in a complete dictionary, but instead | |||
looks for a set of common misspellings. Therefore it might catch errors like | |||
"adn", but it will not catch "adnasdfasdf". | |||
|
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.
See #1535 (comment) for more detail of fixes.
Co-authored-by: Peter Newman <[email protected]>
Don't spellcheck README.md
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.
🎉
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.
Sorry @bl-ue , we can't just skip the whole of README.rst because of one (deliberate) typo! How daft is codespell going to look when it ships a readme with typos in it?!?
The ideal solution is to check readme separately and ignore just the one or two deliberate typos (via ignore words). The more general solution for other people where it's less critical would be to ignoreit across the entire codebase. We should really use the ideal solution given what we're representing!
Are you happy to re-engineer the CI tests then after this @bl-ue , or do you want me to? |
I'm sorry! That's what we get with my eager merging 😝😆
You mean update the CI to only ignore the specific typos in the readme? Sure, I'll do it! |
😄
The gold-plated solution would probably be best, skip the readme as you've done in the main run, but add another run which checks just the readme but ignores the additional deliberate typos, then we won't get "adn" all over the rest of the codebase. |
Good idea. I'll do it 👍🏻 |
thanks y'all! |
No problem @tir38 — thank you for evaluating codespell! I'd recommend some other tools that are probably more what you're thinking of when you hear spellchecker: |
Hahaha — sorry @peternewman! 😂 |
I spent way too much time figuring this out the hard way.