reserved names

Question

Hi Jan,

Please advise regarding reserved names in Javascript within medini analyze.

For example, I can always examine the contents of a variable named "selected" to find out what metamodel objects the user has selected in the current project.

For example, I can also use "var projects = Global.getProjects();" to find out what projects are available for the user to select.

What I would like to know is: I can ensure that I do not experience any namespace collisions by avoiding names used in the libraries provided to us ("excel.js", "ui.js", etc...). But, in order for me to avoid namespace collisions with things like "selected" and "Global", is there a list of such reserved names that we can sticky to a post?

I think understanding what names are reserved by medini analyze would be useful.

Thanks in advance, kind regards!

medini_1028367136 · Answer

Jan, thanks for your help with this, I looked at the in-tool documentation and it's very helpful. I will take a look at the example you provided also.

Thanks again!

medini_1024169437 · Answer

Hi Roy,

very good question. So first of all all names that are predefined by the medini scripting runtime are describe din the "analyze Scripting and API documentation". There yo find objects and variable names as Selection, Global, Metamodel or __tool_version etc.

The problem with name clashes when using the script libraries is a bit different. When we started to write libraries we unfortunately missed to have the name clash issue in mind right from the beginning. So just writing libraries that define arbitrary functions and variables increases the possibility of name clashes.

In this article (https://medini.freshdesk.com/solution/articles/1000263224-how-to-modularize-your-scripts) at the very end (Tipp II) I explain how it could be done better. In principle define anonymous objects that you can assign to arbitrary namespaces when loading them.

So I think at some point in time we have to port all libraries to this approach.

Would you agree on that?

Happy Scripting

Jan