A note on console log

Question

A colleague recently run into a strange problem. He used

console.log(element.label);

to log element and event names to the script console. All was working but suddenly the script stopped working with:

What has happened? It turned out that one element made the script fail and that element has { or } in their name or label.

As you can see in this article from long time ago, medini uses a special formatter that is using {0} as placeholder in the first argument to log function. So the fix was to use:

console.log("{0}", element.label);

Happy Scripting

Jan

medini_1024169437 · Answer

Hm, not sure, maybe something was not working after uncommenting, or as the comment implies, this will only work with 23.1?

jan

medini_1040753747 · Answer

Thanks Jan! Totally forgot to look there. Looking at the script... do we need to uncomment these lines when going to version 2023?

// we are interested in any connector, specifically when changing it
// 23.1! eClassFeaturesList.push(Metamodel.sysml.SysMLConnector);
// 23.1! eClassFeaturesList.push([Metamodel.sysml.SysMLRelationship.the_source_element, Metamodel.sysml.SysMLRelationship.the_target_element]);

medini_1024169437 · Answer

Johan, this is coming from the hook script we provided you a while back, to avoid changing the diagram accidentally.

Please check the handleElementCreated() function.

Jan