search

jiller / agentsmithplugin

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

IdentifierWordIsNotInDictionary disable comment not functioning! #170

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?

1. Supress the dictionary

What is the expected behavior? What do you see instead?
Inserts comments like so

// ReSharper disable IdentifierWordIsNotInDictionary
        public void MyMethod()
// ReSharper restore IdentifierWordIsNotInDictionary

What version of ReSharper, Visual Studio and Windows do you use?
Windows 7, resharper 5.1, VS 2010

Please provide any additional information below.

It would be really helpful to just disable spell checker on a class level, 
project level or even method level.. i.e. option to not check spelling of 
methods in a certain class.

Original issue reported on code.google.com by madridjo...@gmail.com on 31 Jan 2011 at 10:31

GoogleCodeExporter commented 8 years ago 
Spell checking is disabled after '//agentsmith spellcheck disable' comment and 
before '//agentsmith spellcheck restore'

Original comment by forever....@gmail.com on 2 Feb 2011 at 10:40

GoogleCodeExporter commented 8 years ago 
Well here it continues to display the squiggly line underneath the word.

Original comment by madridjo...@gmail.com on 2 Feb 2011 at 10:54

GoogleCodeExporter commented 8 years ago 
Still a problem in V1.5 beta 4 - JetBrains are not forthcoming with an easy way 
of detecting the disable comments. Possibly will have to write our own (this is 
how it was supposed to have worked in 1.4.x).

Original comment by cds...@gmail.com on 15 Jan 2012 at 12:46

GoogleCodeExporter commented 8 years ago 
We are hoping to be able to use your new AgentSmith plugin for v6.1, but in 
order to do so we really need this feature as we rely heavily on it at the 
moment.

We had the same problem our plugin using the disable / restore comments and 
recently discovered a solution. Maybe the solution will work for you too.

If you implement the check using a "ProblemAnalyzer" instead of a "DaemonStage" 
and "DaemonStageProcess", then the infrastructure from ReSharper automatically 
implements the disabling for you.

To do this your ProblemAnalyzer class must have an attribute 
"ElementProblemAnalyzerAttribute ". There is a generic base class class 
"ElementProblemAnalyzer", which you can use.

In addition I think the Highlighting class needs to be marked with 
ConfigurableSeverityHighlightingAttribute. The Id used for the Highlight is the 
identifier that will be used in the disable / restore comments.

I have attached the code that we used for our check. 
Regards,
Helen Ross

Original comment by JHelenR...@googlemail.com on 16 Mar 2012 at 3:33

Attachments: