[General] Multiple nodes do not find their parent node anymore with "getOrThrow"

borkdominik / bigUML

A UML web modeling tool based on GLSP, distributed via a VS Code extension.

MIT License

32 stars 5 forks source link

Closed deweiiss closed 1 year ago

deweiiss commented 2 years ago

nodes which worked fine are not creatable anymore
getOrThrow does not find parent node via modelIndex.getSemantic(operation.getContainerId()) anymore for some reason
some of the nodes where tested 2 weeks ago and worked fine -> activity diagram is heavily affected at the moment

deweiiss commented 2 years ago

follows issue #57