Dependencies between increments

[hohwille]

Actually increments often have dependencies on each other. So e.g. for CRUD there is the REST service that depends on the logic what relies on TOs and DAOs that again depend on entity infrastructure. These dependencies are currently not expressed.

CobiGen should offer a way to express such dependencies (references via IDs and not via display names of course).

The next question is how to deal with this information in the UI. IMHO a big problem at the moment is that new CobiGen users that do not know the architectural details (what should be an important stakeholder for CobiGen) do not know of the dependecies and hence are clueless what to select and what combination will lead to a working result on an initial generation.

However, Power-Users still need the flexibility to select whatever they like as e.g. for Re-generation it can make absolute sense to violate the dependencies.

Maybe the best way would be to visualize the dependencies somehow (maybe as tree?). Also it would make sense to allow an option so that if I select an increment then dependent increments are automatically selected as well.

[maybeec]

You can nest increments in the templates specification or include any increments to another increment by id reference, see Increments documentation.

Although, this dependencies are also shown in the UI, there is some space for improvements, I guess. I think this is a valid point to be investigated to get an even more convincing solution.

[github-actions[bot]]

Stale topic. Please negotiate closing or discussing the relevance of this ticket.