#spellcheck #spelling #grammar

app cargo-spellcheck

Checks all doc comments for spelling mistakes

77 releases

new 0.9.4 Nov 24, 2021
0.9.0 Oct 30, 2021
0.8.11 Jul 26, 2021
0.8.0-alpha.0 Mar 18, 2021
0.3.0 Jul 29, 2020

#74 in Text processing

Download history 63/week @ 2021-08-09 181/week @ 2021-08-16 46/week @ 2021-08-23 44/week @ 2021-08-30 69/week @ 2021-09-06 84/week @ 2021-09-13 108/week @ 2021-09-20 193/week @ 2021-09-27 145/week @ 2021-10-04 100/week @ 2021-10-11 165/week @ 2021-10-18 88/week @ 2021-10-25 159/week @ 2021-11-01 162/week @ 2021-11-08 86/week @ 2021-11-15 98/week @ 2021-11-22

488 downloads per month

MIT/Apache

7.5MB
12K SLoC

cargo-spellcheck

crates.io CI commits-since rust 1.51.0+ badge

Check your spelling with hunspell and/or nlprule.

Use Cases

Run cargo spellcheck --fix or cargo spellcheck fix to fix all your documentation comments in order to avoid nasty typos all over your source tree. Meant as a helper simplifying review as well as improving CI checks after a learning phase for custom/topic specific lingo.

cargo-cpellcheck is also a valuable tool to run from git commit hooks or CI/CD systems.

Check For Spelling and/or Grammar Mistakes

cargo spellcheck check
error: spellcheck
   --> src/main.rs:44
    |
 44 | Fun facets shalld cause some erroris.
    |            ^^^^^^
    | - shall or shall d
    |

Apply Suggestions Interactively

cargo spellcheck fix
error: spellcheck(Hunspell)
    --> /media/supersonic1t/projects/cargo-spellcheck/src/literalset.rs:291
     |
 291 |  Returns literl within the Err variant if not adjacent
     |          ^^^^^^

(13/14) Apply this suggestion [y,n,q,a,d,j,e,?]?

   lite
   litter
   litterer
   liter l
   liters
   literal
   liter
 ยป a custom replacement literal

Installation

cargo install --locked cargo-spellcheck

The --locked flag is the preferred way of installing to get the tested set of dependencies.

๐ŸŽˆ Contribute!

Contributions are very welcome!

Generally the preferred way of doing so, is to comment in an issue that you would like to tackle the implementation/fix.

This is usually followed by an initial PR where the implementation is then discussed and iteratively refined. No need to get it all correct the first time!

Documentation

Dependencies

~16โ€“23MB
~475K SLoC