Open eclipse-viatra-bot opened 6 months ago
By Zoltan Ujhelyi on May 26, 2016 08:33
Moved to 1.4
By Abel Hegedus on Sep 06, 2016 10:13
Postponing issues to 1.5
By Zoltan Ujhelyi on Jan 25, 2017 07:45
Mass move of tickets we are not expecting to solve soon to the Future milestone.
By Zoltan Ujhelyi on Oct 04, 2017 05:26
Moving potential tasks from future to 2.0.
By Zoltan Ujhelyi on Feb 08, 2018 07:21
Postponing to a future release.
By Zoltan Ujhelyi on May 27, 2019 07:49
Bugzilla cleanup.
By Zoltan Ujhelyi on Nov 20, 2019 05:51
Postponing issues to the next release.
By Zoltan Ujhelyi on May 18, 2020 13:04
Postponing issues that will not be solved for version 2.5.
By Zoltan Ujhelyi on Nov 23, 2020 08:30
Mass postponing of issues to the 2.6 timeframe.
| --- | --- | | Bugzilla Link | 492146 | | Status | NEW | | Importance | P3 enhancement | | Reported | Apr 21, 2016 03:38 EDT | | Modified | Nov 23, 2020 08:30 EDT | | Version | 1.2.0 | | See also | 565611 | | Reporter | Abel Hegedus |
Description
When looking at bug 491100 we identified that error markers on an annotation translate into PErrors in the PSystem representation on the pattern itself. This functionality is implemented in the PatternSanitizer class.
Since errors reported by annotation validators (and placed on the annotation or its parameters) do not interfere with basic pattern matching (e.g. loading into the Query Explorer), this approach could be refined to differentiate between erroneous patterns and patterns with annotation errors.
Users of PAnnotations should be able to either detect that a given annotation is erroneous or the PQuery should not even return problematic annotations.
Additionally, we could also extend PAnnotation to be able to store and return PProblems, similar to PQuery.