snapbox
typos
snapbox | typos | |
---|---|---|
6 | 19 | |
111 | 2,174 | |
2.7% | 10.5% | |
9.4 | 9.5 | |
6 days ago | 22 days ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
snapbox
-
Announcing diff.rs!
If needed, here is an example of per-word diffing and highlighting of trailing newline differences.
-
Trycmd just ignores my tests
I see. I would try writing the same name as in your Cargo.toml. For example, if yours was toml [package] name = "caesor_cipher" I would try bin.name = "caesor_cipher" It seems that trycmd might ignore a test if the bin.name field is incorrect: https://github.com/assert-rs/trycmd/issues/105
-
Rust: A Critical Retrospective
I find rustdoc lacking for clap. rustdoc does a good job with API reference documentation and is improving in its handling of examples but derive reference and tutorial documentation are a weak point.
For examples, its improving with the example scraping work (e.g. https://docs.rs/clap/latest/clap/struct.ArgMatches.html#meth...) but testing of example is still lacking. I've written trycmd to help (https://github.com/assert-rs/trycmd).
For derive reference and tutorial documentation, your choices are
- A very long, hard to navigate top-level documentation, see https://docs.rs/structopt/latest/structopt/
- External documentation, see https://serde.rs/
- Dummy modules to store your documentation (I've seen this used but can't remember one off the top of my head)
For clap, my documentation examples are best served as programs and we've had a problem with these being broken. The Rust CLI book has a decent strategy for this by pulling in code from external files (https://rust-cli.github.io/book/index.html). I was tempted to do that for clap where example code and output (all verified via trycmd) are pulled into an mdbook site but I've stopped short and just have a README that links out to everything (https://github.com/clap-rs/clap/blob/master/examples/tutoria...). Its not great.
-
Great thanks to the rust community for having a book (sort of like the rust book) for some crates as well. Makes everything infinitely approachable
Another problem we found in clap was it was easy for our examples to build but harder to make sure they worked. This is why I wrote trycmd (example "tests").
-
ANN: `trycmd` v0.7.0 released!
Would love feedback on on some of the known questions or whatever else is on your mind!
-
trycmd: Snapshot testing for a herd of CLI tests
The design is inspired by trybuild with thought given to how mdBook books could pull in content so you can verify a code sample, the command for running it, and the output. In considering how to keep clap's website up-to-date, I had this idea and threw it together to see how well it works. Overall, seems good with room for improvement. I'll have to give this a try on a real world program soon.
typos
- Get rid of typos in your repo; for code and documents
-
Shebling: Rewriting ShellCheck in Rust
There is typos though that takes a bit different of an approach to spell checking. When the default is to ask the user (like in a text editor), a regular spell checker is likely better. typos is more meant for being run in an automated fashion.
-
I'm making custom cursor library. I need some feedback
I recommend you run https://github.com/crate-ci/typos
-
[Gitoxide in February]: `git-repository` is now `gix`, and statically known git-config keys
Oh yeah, I can see you short hashes being a problem. The challenge has been finding the right heuristic for them
-
LanguageTool-Rust v2 releases š: using LanguageTool grammar checker with Rust
Is there good usage examples for this tool? typos simply traverses directories on invocation, wonder if there's a static analysis equivalent for ltrs.
-
Ladies & Gentleman, this is why Iām a Senior Software Engineer
highly recommend adding https://github.com/crate-ci/typos to your CI...very easy to add to a github action, catch fun spelling errors even in camelCased and snake_cased variable names...catch em before they become public facing APIs
-
Visual Studio Spell Checker Preview Now Available
I like to use https://github.com/crate-ci/typos as a command-line option. It's built to run as a service or in CI... I run it in our code review software and it has been a big hit.
-
Typos-CLI ā Source code spell checker
there's a little comparison table here https://github.com/crate-ci/typos/blob/master/docs/comparison.md
-
How to fix typos in your code for goods !
typos
What are some alternatives?
clap-rs - A full featured, fast Command Line Argument Parser for Rust
spellsitter.nvim - Treesitter powered spellchecker
biscuit - Biscuit research OS
codespell - check code for common misspellings
browser - Create Elm programs that run in browsers!
vim-abolish - abolish.vim: Work with several variants of a word at once
steam-for-linux - Issue tracking for the Steam for Linux beta client
hunspell - The most popular spellchecking library.
cargo-public-api - List and diff the public API of Rust library crates between releases and commits. Detect breaking API changes and semver violations via CI or a CLI.
dictionaries - Hunspell dictionaries in UTF-8
heapless - Heapless, `static` friendly data structures
unix-history-repo - Continuous Unix commit history from 1970 until today