- The new ErrorHighlighting Profiles are awesome! All the
major problems have been fixed.
- Now possible to easily run Analyze->Inspect on a file
with the exact same settings as your Error Hilighting
profile. This is great when there are many of the same
problem like "missorted modifiers", becuase the
Inspection Results window lets you apply quick fix en
- The 'Edit options of "xxxx"' Intention is very nice!!
- The 'Edit options of "xxxx"' Intention pops up the
dialog and highlights the option name, but many times it
is not visible. I usally have to scroll up a few lines
to see it.
Other ideas for improvement:
- Inspection Results Window.
Clicking on Inspection name should display the
full description in the pane on the RHS. Currently the pane is
blank when you click the inspection name.
- At the top of the Editor Pane gutter, there is that
little red/yellow/normal colored square showing the
highest severity error in the file. If you mouse over
the square at the top of the gutter, it says something
like " Analsys completed. 50 warnings found." If you
double click that square, I think it should
automatically run inspect file with the ErrorHilighting
Then, when I come upon a file with a bunch of warnings, I
can double-click the square and immediately see the
inspection results window where I can apply fixes en
- The "Edit Options" choice with ALT+ENTER in the
Editor pane is very useful. I would like this option
in the Inspection Results window also.
- I would like a hilighting level below warning called
notice. The notice hilighting wouldn't show in the
gutter, but if you were looking at the code, the
expressions tagged by the inspection would be hilighted.
This is useful for certain constructs/code where you
would like it flagged because it might be non-standard,
but you don't want to flag it as an error/warning because
it could be fine.
There are a bunch of inspections which I have had to turn
off because there are too many exceptions where it is ok,
but if I could still hilight them in the Editor Pane
without gumming up the gutter, I would still enable them.
- As mentioned in another thread, I would like to assign different ErrorHilightingProfiles for different packages / workspace paths.
- I would like quickfixes for naming convention.
(Not sure if that is possible?)
You could compare the incorrect name to the pattern and
change the minimum number of chars to fix it?
Only apply the quickfix if it only required (1)
changing case of characters (2) adding fixed text from
For example, with pattern m[A-Z][A-Za-z] for field, if
I have incorrect field name "id", quickfix could change
it to " mId". But if I have a field "id23422" or
"id_something", then it shouldn't apply the fix.
- Parameter name differs from parameter in overidden
-- I like this inspection to help keep my code
but it also reports when I override methods from the
JDK and other libraries. I would like option to only
check my project's classes..
-- The default equals and hashCode() implementaiton from
Code->Generate, is flagged by Inspect as having
problems. The 'conditional expression'. It would be
nice if IDEA's generated code passes all inspections
(except in cases where two inspections contradict one