Yeah I know it's not a big deal, but I'm working on some other patches and I noticed some spelling mistakes, so I ran codespell and made a patch to clean up the entire code base. Only 5 corrections!

CommentFileSizeAuthor
#3 2922828-3-spelling.patch5.33 KBtr
#2 2922828-spelling.patch4.93 KBtr
spelling.patch3.12 KBtr

Comments

TR created an issue. See original summary.

tr’s picture

tr commented
StatusFileSize
new 2922828-spelling.patch4.93 KB

Four more corrections ...

tr’s picture

tr commented
StatusFileSize
new 2922828-3-spelling.patch5.33 KB

And one more. Let's try the testing again ...

jonathan1055’s picture

jonathan1055 commented

Minor, but still important. Thanks for doing this.

so I ran codespell

- I've done a quick google search for this and it looks like a useful thing. How did you run it? Seems like it is a node.js CLI tool, so maybe it might be worth loading and running it in the rules travis builds? I am trying to work on running ESLint in .travis.yml (no issue for that yet, but I have some work in progress in my eslint branch https://travis-ci.org/jonathan1055/rules/builds/288490761) Codespell could be added in a similar way?

tr’s picture

tr commented

It's a python script, something that came up in the core issue queue years ago. It only catches isolated words, not compound words in camelCase, which is why I amended my patch several times as I perused the codebase.

After the first pass using it and correcting errors, you rarely have to do it again - misspellings are slow to creep into the codebase.

Find it at https://github.com/lucasdemarchi/codespell
It does require python. Instructions in the README.

  • fago committed 31029b8 on 8.x-3.x authored by TR 
    Issue #2922828 by TR: Spelling
fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Needs review » Fixed

Thanks, pushed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.