 |
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Eugene Vigdorchik - 09 Aug 07 17:38
It does not influence the green color of error stripe, yet providing feedback on symbol access that is truly dynamic. I doubt this highlightig should be disabled.
I am not asking for it to be disabled, I'm asking for the ability to control it at the user's discretion.
The feedback it supplies is so voluminous in so many cases that it obscures other inspection feedback. It should be user-configurable. Perhaps a "code style" setting for such expressions would be a better UI? (In addition to having the inspection available)
Similar to how I can assign a separate style to "re-assigned variables" in the Java code style, in addition to the inspection that can batch-inspect code and report such occurrences. cannot determine type statically is not an inspection, it is ajust a highlighting like Taras mentiones.
Terminology notwithstanding, can the user be given control over this feedback?
Given the nature of Groovy, it is often excessive and tends to obscure other problems. Perhaps allowing the user to specify something about the context of their code (e.g., Grails code) so a better heuristic can be applied. Randall, I think you want a seperate "Groovy" Colors&Fonts tab, with (at least) an entry for "dynamic symbol access".
In addition an inspection doing the same thing could be provided to see such usages for the whole project. (if someone actually is interested?) |
|||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
New Feature
Open
Normal
Provide Selective Control Over Groovy Code Inspections