Inspections Plugin Request

I just round where the inspections plug-in puts the inspections under the
errors area. They all defaulted to do not show. Is there a way to make
them default to As Warnings?

You don't want to know how long it took to go through and set 85% of them on
to the second value in a three drop-down list. Argh.

BTW, Great plug-in! The very best.

--
Norris Shelton
Web Developer
Sun Certified Java Programmer
Appriss, Inc
502-815-3825
YIM: norrisshelton
AIM: NorrisEShelton
MSN: norrisshelton@yahoo.com
ICQ: 26487421


5 comments
Comment actions Permalink

There is a performance impact with having all inspections run against each file. Myself and the team I work with prefer to use a minimal set for normal working activities and inspect the code base for a larger set in an offline manner. Defaulting everything to warning would cause the opposite problem for us to remove the warning on most items.

0
Comment actions Permalink


As someone who just lost their settings in upgrading to 1080, I can totally sympathize. I've got to go through set most of them to yellow as well, and yes, it's a total pain. I'd love some way of setting a large number of them at once. Defaulting to yellow is probably overkill, particularly since there are about a half-a-dozen inspection pairs which are directly contradictory, and there are performance implications for inspections (although a lot less than one might imagine).

Unfortunately this discussion is moot, as that level of configuration is completely owned by JetBrains, and there is nothing a plugin can do to change it. You'll need to come up with a Tracker entry for this, as my hands are tied.

Glad you like the plugin. Version 0.0.9 coming soon!

--Dave Griffith

0
Comment actions Permalink


Not to disagree, but such timings as I've been able to do show there's not much cost to most of the on-line inspections, if the inspections aren't violated. Evidently, creating and rendering error/quick-fix objects takes a lot more time than actually figuring out where the offending constructs are. TheTurning on any given inspection is only going to cause a noticable on-going performance hit if you regularly violate that inspection, and don't often fix it.

--Dave

0
Comment actions Permalink

Dave Griffith wrote:

>As someone who just lost their settings in upgrading to 1080, .. I'd love some way of setting a large number of them at once. Defaulting to yellow is probably overkill, particularly since there are about a half-a-dozen inspection pairs which are directly contradictory, ..
>Unfortunately this discussion is moot, as that level of configuration is completely owned by JetBrains, and there is nothing a plugin can do to change it. You'll need to come up with a Tracker entry for this, as my hands are tied.
>

>

see:
IDE Settings - errors : add saveable profiles , as in "Code
Inspection", and..
http://www.intellij.net/tracker/idea/viewSCR?publicId=15113


Alain

0
Comment actions Permalink

I put on my +1

"Alain Ravet" <alain.ravet.list@wanadoo.be> wrote in message
news:btn9nl$u2i$1@is.intellij.net...

Dave Griffith wrote:

>

>As someone who just lost their settings in upgrading to 1080, .. I'd love

some way of setting a large number of them at once. Defaulting to yellow is
probably overkill, particularly since there are about a half-a-dozen
inspection pairs which are directly contradictory, ..

>Unfortunately this discussion is moot, as that level of configuration is

completely owned by JetBrains, and there is nothing a plugin can do to
change it. You'll need to come up with a Tracker entry for this, as my
hands are tied.

>
>
>

>

see:
IDE Settings - errors : add saveable profiles , as in "Code
Inspection", and..
http://www.intellij.net/tracker/idea/viewSCR?publicId=15113

>
>

Alain



0

Please sign in to leave a comment.