Hi Math,
The toolset does not forbid cyclic dependencies which could potentially lead to a stackoverflow exception during generation, like in your case. This is a current limitation of the example generators not checking cyclic references.
Also, function blocks cannot reference other function blocks at the moment.
What use case do you have in mind to implement with Vorto which requires cyclic dependency?
Cheers, Alex

Im trying to make a generic generator, what creates SQL tables from the modell, so my problem is, when i create tables, multiple tables can be created for the same entity. I walk trough the infomodells, the referred functionblocks and lastly the referred Entities and Enums. But this issue comes to my mind when i checked some example codes, and it contains entities with referred entities. So one way its possible, but two-way is forbidden?

from a moddeling perspective we do not permit that. So please create two entities and drag and drop them to each other in the "DataType Models"-Perspective. I assume that most of the existing code generators will not work with that cyclic dependency. This is something that we should have in mind and find a solution for it. But for your use-case and your specific code generator this should be possible.

Let us know if this helps! Are you going to contribute the new code generator to the Vorto project?

I will check it today later but for the first blink i have to say, if i drop one entity to the other in the DataType Perspective, it creates a reference (Ive tried it already). But what i want is an actual attribute of the Entity(like how i explained in the topic opener), couse during the code generation, i walk trough the properties of the elements. I guess now this kind of reference is forbidden, but correct me.

I havent make my decision about the contrubution, first of all it must be a useful, working generator, to make sense of sharing

The reference that you are describing in your initial question is possible. The way you are modelling entity alpha and entity beta is correct. You only need to make sure that in entity alpha the entity beta is imported by means of a corresponding "using" statement. A corresponding "using" statement must also be available in entity beta for importing the entity alpha.

Thanks the help, i can finally make this example! The good thing is my generator doesnt goes crazy with this type of infinite loop, but the bad thing is it doesnt even recognize it like a Entity property. i have to do some work with it, and hopefully i can fix it. Thanks the help!

Finally i solved to force my generator working perfectly. Thanks for the help, but i have another question.
Its a bit different topic, but i hope that you wouldnt mind if i ask it here So...

I want to make my generator a bit generic, so after the rightclick->generate order, somehow you can manipulate the sort of database, language of the generated code, etc. Is there any option, to provide a bunch of variations, parameters to the user, during the code generation?

I have just read your question regarding the provisioning of parameters for your Generator. Our Virtual Developer Platform allows you to define such parameters for generators that run on it. Also, in relation to Vorto, Virtual Developer lets you ...

deploy and execute existing Vorto generators (we are currently working on a proof of this by doing it for one of the exmple generators of Vorto)

develop generators that access the Vorto model repository remotely, through their REST-API

develop generators that consume Vorto models in form of a set of model files