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 a sorted wordcount to the bottom of all_pod_files_spelling_ok #7
Conversation
Cool! I'd want to see this in descending order, though. |
@xdg, Ascending order was chosen mostly because of how terminal scroll means the most significant are more likely to stay "in screen" at the end of a test run, though I'll gladly flip the orientation if its deemed necessary =) I could probably make it nicer still by grouping by frequency instead of having a mass of =1. |
That's a good point. Most of the time I have only a dozen or so words so it doesn't really matter. So I take it back. I'm neutral on the direction. |
This is the revised format I'm working on, I think its much easier on the eyes:
|
How about "All incorrect words, by number of occurrences:" |
This makes nuking the most commonly misspelt words easier if you're working on a large project with a lot of files, by helping you easily see what needs to be deemed a "stopword" and what needs to be hit with an edit pass.
Now patched and squashed as follows:
( NB. Differences in lists of words is because I'm prototyping my changes on a non-test-spelling codebase, so no need for concern, the list with "resultset" as the most common is Test-Spelling's Pod checks, and the one with 'subquery' is extracted from the comments: https://github.com/kentfredric/dbix-class/blob/topic/spelling.t/xt/commentspelling.t#L57 ) |
Add a sorted wordcount to the bottom of all_pod_files_spelling_ok
Awesome. Thank you @kentfredric! I will ship this in a few days when I return from my trip. |
POSTing upload for Test-Spelling-0.20.tar.gz to https://pause.perl.org/pause/authenquery |
This makes nuking the most commonly misspelt words easier if you're
working on a large project with a lot of files, by helping you easily
see what needs to be deemed a "stopword" and what needs to be hit with
an edit pass.
This was an an apparent issue when I was adding a pod spelling check to dbix-class, which had 80 subtests worth of spelling failures which was hard to make sense of.
After this patch, it emits the following at the end:
Which indicates
resultset
is either a good candidate for a stopword or a universal translation =).Though "All wrong words" seems awkward and forceful, but I couldn't think of a better suggestion.