| Summary: | Invalid egdes with unsynchronized mode | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] Sirius | Reporter: | Laurent Redor <laurent.redor> | ||||
| Component: | Diagram | Assignee: | Laurent Redor <laurent.redor> | ||||
| Status: | CLOSED FIXED | QA Contact: | Pierre-Charles David <pierre-charles.david> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | maxime.porhel, pierre-charles.david | ||||
| Version: | 0.9 | Keywords: | triaged | ||||
| Target Milestone: | 1.0.0M7 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
When checking whether the existing edges must remain in unsynchonized diagram, it lacks a control to determine if the semantics source and target are always OK according to sourceFinderExpression and targetFinderExpression of the mapping. See org.eclipse.sirius.business.internal.experimental.sync.DEdgeSynchronizerHelper.handlePreviousCandidates(Collection<DEdgeCandidate>, Iterable<DDiagramElement>, EdgeMapping, Map<EObject, Collection<EdgeTarget>>, Map<EObject, Collection<EdgeTarget>>) in stillCandidate predicate. Fixed through commit c088cb034e68b59d082d0c26043dbff111f9c266: http://git.eclipse.org/c/sirius/org.eclipse.sirius.git/commit/?id=c088cb034e68b59d082d0c26043dbff111f9c266 Verified on 1.0.0M7rc1 (1.0.0.20405030833). Available in Sirius 1.0.0M7 (see https://wiki.eclipse.org/Sirius/1.0.0M7 & http://git.eclipse.org/c/sirius/org.eclipse.sirius.git/tag/?id=v1.0.0M7). |
Created attachment 240583 [details] Use case for the steps to reproduce It is possible to have incoherent edges visible on an unsynshonized diagram. Steps to reproduce: * Import the project of unsyncReconnectUseCase.zip * Open the 2 diagrams (DiagramWithReconnect-Sync and DiagramWithReconnect-unsync) * In DiagramWithReconnect-Sync, move the edge from NewEClass to NewEClassChange. * In DiagramWithReconnect-Unsync, the edge would have to disappear : KO