Bug 573666 - Make ValidationMarkerManager extensible
Summary: Make ValidationMarkerManager extensible
Status: CLOSED MOVED
Alias: None
Product: Sphinx
Classification: Automotive
Component: Validation Runtime Extensions (show other bugs)
Version: 0.11.0   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: 0.12.1   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-20 09:27 EDT by Snejana Bisa CLA
Modified: 2024-05-08 14:58 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Snejana Bisa CLA 2021-05-20 09:27:32 EDT 
There are use-cases that require customizing the validation marker management implementation. 
An example could be handling of a diagnostic whose data needs to be further processed to reach the actual target EObject. 
Check org.eclipse.sphinx.emf.validation.markers.ValidationMarkerManager.addMarkers(Resource, Diagnostic), line 176:

EObject tgtObject = (EObject) childDiagnostic.getData().get(0);

//retrieve the actual target element
 EObject actualTargetObject = unwwap(tgtObject);

attributes.put(EValidator.URI_ATTRIBUTE, EcoreUtil.getURI(actualTargetObject ).toString());
(...)
Comment 1 Balazs Grill CLA 2024-05-07 00:58:08 EDT 
This issue will be migrated to gitlab.
Comment 2 Eclipse Webmaster CLA 2024-05-08 14:58:18 EDT 
This issue has been migrated to https://gitlab.eclipse.org/eclipse/sphinx/org.eclipse.sphinx/-/issues/4.