If my JAVA file has syntax errors (e.g. duplicate method declarations), my injected Annotator is not called at all. While this may be the right thing, is there a way to customize this behaviour?
If my JAVA file has syntax errors (e.g. duplicate method declarations), my injected Annotator is not called at all. While this may be the right thing, is there a way to customize this behaviour?
well, IMHO it is distracting for the user to see all annotators go away and come back after fixing just one error - the user does not necessarily understand the difference between (syntax) annotators provided from Language itself and contributed annotators.
If my JAVA file has syntax errors (e.g. duplicate method declarations), my injected Annotator is not called at all. While this may be the right thing, is there a way to customize this behaviour?
If my JAVA file has syntax errors (e.g. duplicate method declarations), my injected Annotator is not called at all. While this may be the right thing, is there a way to customize this behaviour?
Hello Yann,
Not at the moment. Do you need such a thing?
-
Maxim Shafirov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
Hi Maxim,
well, IMHO it is distracting for the user to see all annotators go away and come back after fixing just one error - the user does not necessarily understand the difference between (syntax) annotators provided from Language itself and contributed annotators.
Greetings,
Yann
Yann Cebron wrote:
This is issue http://jetbrains.net/jira/browse/IDEABKL-3420 and it's a
huge problem for my language plugin as well.
Also http://jetbrains.net/jira/browse/IDEA-5520 concerns this issue
Yann Cebron wrote:
And yet another question: how can I force re-run of Annotator on a given file to update the status resulting by changes in other files?
bump