Spellchecking type names, identifiers and strings

[hunger]

Is your feature request related to a particular use-case?

No.

Describe the solution you'd like to implement/see implemented

cargo-spellcheck is checking my documentation , which is great. But this is not place I can put spelling mistakes that are user visible:-)

Could cargo-spellcheck optionally also check strings? Those are likely to be seen by users.

In addition it would be cool to also spell check identifiers (variable names, type names, etc.), which I consider also to be user visible strings in he case of library crates.

Describe alternatives you've considered

Using the cspell plugin in VS Code:-)

Additional context

Some rules to split identifiers in snake_case or CamelCase will be needed of course.

[drahnr]

Related #196
Mildly related #201

TL;DR

yes, this is possible, but requires some effort on the parsing front. There could be an alt layer like, CommonMark / Markdown are abstracted, there could be an IdentLayer that covers a file and relevant, non-keyword identifiers.

Somebody just needs to put in the effort to extract those.

Note: Currently both syn and ra_ap_syntax are used for parsing, it might be a good idea to unified towards ra_ap_syntax first.