Interactive fixing seems buggy about cargo-spellcheck HOT 3 OPEN

Hey, thanks for the candid feedback. You can achieve checking only changed files using `git diff --files $branchbase..HEAD which usually is the preferred mode of usage. Line based is more difficult since the tokenizer requires context of possibly multiple adjacent lines.

If there are multiple issues in the same line or detected by multiple checkers you get duplicate suggestions which might break individual lines. See issue #10 #232 #171

As always, I am very happy to review PRs or onboard people to the codebase

from cargo-spellcheck.

You can achieve checking only changed files using `git diff --files $branchbase..HEAD which usually is the preferred mode of usage.

Thank you. That changes things. I'll give it a try.

If there are multiple issues in the same line or detected by multiple checkers you get duplicate suggestions which might break individual lines.

Yes. That might be it. Unfortunately out codebase has so many typos in comments, that I'm hitting it all the time. Though I've also noticed my actions just ... getting lost.

from cargo-spellcheck.

Is the codebase open source? Could you provide a sample doccomment file where the issue pops up?

from cargo-spellcheck.