Open kayhayen opened 5 years ago
I know nothing about vscode, but it's my understanding that our problem matcher: https://github.com/codespell-project/codespell-problem-matcher/blob/master/codespell-matcher.json
Is based on the same/similar syntax to the vscode one.
I'm assuming you can just run a program across the code and feed the output into a matcher to generate the problems tab content?
Originally posted by @peternewman in https://github.com/codespell-project/codespell/issues/1875#issuecomment-775232960
Are there any news about this topic? I have no idea about how VSCode works itself, but I already integrated a few linters into other IDEs such as Neovim.
Should the solution be implemented here, or in a separate repository implementing a new VSCode extension?
Maybe it is easier if an intermediate plugin with a higher abstraction layer is used, such as Linter by fnando. This one already searches for the executables and handles most of it. It should only be needed to add a new file that parses the output of codespell into the diagnsotics of VSCode. I will try to read a little bit more about how to work with plugin in developer versions in VSCode, but I also have no idea about typescript
I am using @ext:streetsidesoftware.code-spell-checker right now, but it I think it is only cspell based and not codespell, which sometimes finds things on top. I like how codespell is coming from a different angle, namely only reporting what it is sure about. That extension basically will flag anything not know, which is way too much many times.
Hello,
I am a very happy user of codespell for Nuitka. However, I wondered, if you were aware of any extension module that integrates with your spell checker, which seems very well suited for automatic fix proposals as well.
Yours, Kay