Commit 53ae15b3 authored by Philip Makedonski's avatar Philip Makedonski
Browse files

+fixed issue with scope resolution when value assignments are present in


target

Change-Id: Ifc4dfec759167aeab5d3c12d66a22ea489e97a1c
Signed-off-by: Philip Makedonski's avatarmakedonski <makedonski@informatik.uni-goettingen.de>
parent ac911a59
......@@ -113,8 +113,9 @@ public class TDLan2ScopeProvider extends AbstractDeclarativeScopeProvider {
EList<EObject> elements = new BasicEList<>();
for (Connection c : configuration.getConnection()) {
if (context instanceof Message) {
//TODO: quick hack until a better solution is found
ICompositeNode oppositeNode = NodeModelUtils.findActualNodeFor(((Message) context).getTarget().get(0));
String targetGateName = oppositeNode.getText().trim();
String targetGateName = oppositeNode.getText().replaceAll("where\\s+it\\s+is.+", "").trim();
if (targetGateName.startsWith(c.getEndPoint().get(0).getComponent().getName()) &&
targetGateName.endsWith(c.getEndPoint().get(0).getGate().getName())) {
elements.add(c.getEndPoint().get(1));
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment