search

jiller / agentsmithplugin

Automatically exported from code.google.com/p/agentsmithplugin
0 stars 0 forks source link

Spelling search and corrections should behave differently for literals/documentation and identifiers #148

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
For example, I have a method "GetTodaysIoiData".  Agent Smith points out
that "Todays" is not a word, yet "Today's" is.  So it suggests renaming the
method as "GetToday'sIoiData" which is valid in string
literals/documentation, but invalid in identifiers.  In fact, when matching
identifiers, Agent Smith should exclude hyphens and apostrophes from
matching.  If this occurred, then this particular error would only occur in
string literals/documentation.

I've also seen cases where R# suggests replacing an unknown substring with
something that contains whitespace or hyphens.  An example of this is
"Parsable" (able to be parsed).  This, and many other similar words, are
commonplace to programmers.  Agent Smith suggests "Pars able" which again
is reasonable in a literal/documentation, but not an identifier.

- R# 4.5
- Windows XP
- VS 2008 (9.0.21022.8 RTM)

Original issue reported on code.google.com by drewnoakes on 26 Oct 2009 at 8:48