search

EWSoftware / VSSpellChecker

A Visual Studio spell checker editor extension that checks the spelling of comments, strings, and plain text as you type. Supports configuration and various languages.
Other
377 stars 65 forks source link

The code analyzer cannot add words to ignored words files or user dictionaries #277

Open EWSoftware opened 1 year ago

EWSoftware commented 1 year ago

There don't seem to be any provisions for modifying files outside of the containing project of the file on which the code analyzer is running. While it may be possible to add support for ignored words files within the project using the Additional File Items feature, this is rather cumbersome as the ignored words file would have to be added to every project in the solution. Not a problem if there's only one or two but a real issue for large solutions with a large number of projects. The preferred approach is to put the ignored words file in Solution Items but it doesn't seem to be accessible there. Likewise, there don't appear to be any provisions for modifying files outside of the project system (an ignored words file in the global configuration and user dictionary files).

If anybody knows more about how this could be made to work, I would appreciate the help as I haven't been able to figure out a solution.

djurodrljaca commented 1 year ago

Is this the reason that there is currently no convenient way for adding words to the ignore list? From what I noticed you need to manually add the words you want to ignore to the spell checker settings...

EWSoftware commented 1 year ago

For identifier misspellings, yes. For strings and comments, it's done using the tagger so works as it always has.

robertson-bauercontrols commented 1 year ago

To rehash an already closed item, is losing the ability to add\ignore words in the source code worth the balance of having the errors show up in code analysis?

My question: Is it possible for me to disable the code analyzer stuff in my .editorconfig, and have it spell check the code in the same fashion it does with comments in the same files? That way my team can have a consistent user experience with spell checking comments vs code, and not have to do two different things.

Thanks!

EWSoftware commented 1 year ago

Turn off the code analyzer option in the general settings category. You can do it in the global configuration or by an .editorconfig in a specific solution or project.