|
Re: Remove warning/error marker [message #1776926 is a reply to message #1776923] |
Wed, 22 November 2017 20:14 |
|
have a look at org.eclipse.xtext.ui.editor.validation.MarkerCreator
and how it is utilized during validation.
i am not sure if you need to remove or if you need to not to check the fast if expensive is running (i assume then all checks are running as well)
so you might have a look at org.eclipse.xtext.validation.AbstractDeclarativeValidator.getCheckMode()
and do a if on that in your fast check.
then you wont need to remove anything
Twitter : @chrdietrich
Blog : https://www.dietrich-it.de
|
|
|
|
Re: Remove warning/error marker [message #1776932 is a reply to message #1776927] |
Wed, 22 November 2017 21:10 |
|
so you ae not talking about markers but about annotations?
and how do you execute expensive validation?
for me this could be a bug .
org.eclipse.xtext.ui.editor.validation.MarkerIssueProcessor.processIssues(List<Issue>, IProgressMonitor)
seems to add stuff only but not remove existing ones.
can you please create a ticket at github.com/eclipse/xtext-eclipse
org.eclipse.xtext.ui.editor.validation.AddMarkersOperation.execute(IProgressMonitor) deletes the markers.
org.eclipse.ui.texteditor.ResourceMarkerAnnotationModel.batchedUpdate(IMarkerDelta[])
treats thst in the editor.
but thats marker annotations only.
this leaves the xtext annotations unattended
these are handle by org.eclipse.xtext.ui.editor.validation.AnnotationIssueProcessor.
imho the validationjob should use a hybrid of AnnotationIssueProcessor and MarkerIssueProcessor (in ValidateActionHandler)
maybe you can do some digging yourself
Twitter : @chrdietrich
Blog : https://www.dietrich-it.de
|
|
|
Powered by
FUDForum. Page generated in 0.01860 seconds