jiller / agentsmithplugin

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

Don't check spelling in string literals used as arguments for certain known methods #150

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
This code raises a spell check error because 'adca' is not a known word.

    new Guid("012454a3-6014-4339-adca-b5026ad6c937")

I'd like to have a list of known parameters for which string literal 
arguments are ignored.  The Guid example is the one I come upon most often.

Note that I wouldn't expect this to be too clever -- the following would 
still warn:

    var s = "012454a3-6014-4339-adca-b5026ad6c937";
    new Guid(s);

Is it possible to extend the ReSharper value analysis attribute set such 
that I can add this attribute in both internal and external annotations, 
just like I can with [NotNull] and [CanBeNull]?

Original issue reported on code.google.com by drewnoakes on 3 Nov 2009 at 2:23

GoogleCodeExporter commented 8 years ago
You should make them Verbatim strings by putting a @ before the starting quote. 
This has the added benefit that other tools wont complain that they should be 
put in a resource file and etc.

Resharper and AgentSmith both have options to enable ignoring of verbatim 
strings.

Original comment by cds...@gmail.com on 4 Jan 2012 at 1:26