-
Notifications
You must be signed in to change notification settings - Fork 470
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Port FxCop rule CA2204: LiteralsShouldBeSpelledCorrectly #529
Comments
This rule uses StringContent dataflow analysis and should be implementable once we merge #1541 |
#1541 is merged. |
This rule is blocked by absence of Naming service. |
I'd like to draw attention to a bug in the current (pre-Roslyn) CA2204 rule where compound-words in literals are flagged by the rule because it doesn't break the compound-words up despite documentation claiming otherwise ("This rule parses the literal string into words, tokenizing compound words, and checks the spelling of each word or token. "). This also impacts use of For example in my project I have this line of code:
This currently gives me this code analysis build warning:
A workaround is to add the word "readmessages" to my Code Analysis Dictionary file's
(Note it instructs me to use I'd also like to request that the code-analysis rules automatically add any |
Title: Literals should be spelled correctly
Description:
A literal string in a method body contains one or more words that are not recognized by the Microsoft spelling checker library.
Dependency: Dataflow
Notes:
The text was updated successfully, but these errors were encountered: