Is your feature request related to a problem? Please describe.
Currently the user has to define unique aliases (elements) and IDs (connections/relations) for the re-usable assets. If you work with several teams there might come up clashes by coincidence.
Describe the solution you'd like
4 ideas:
A: have macros that automatically create unique IDs (checking the modelrepo for existing IDs to avoid clashes)
B: have the command line pumla make a unique ID proposal
C: outsource this to the editor, e.g. a pumla editor plugin (e.g. for pycharm and VS Code)
D: only have the "pumla update" check for alias/ID clashes and report errors
Is your feature request related to a problem? Please describe. Currently the user has to define unique aliases (elements) and IDs (connections/relations) for the re-usable assets. If you work with several teams there might come up clashes by coincidence.
Describe the solution you'd like 4 ideas: A: have macros that automatically create unique IDs (checking the modelrepo for existing IDs to avoid clashes) B: have the command line pumla make a unique ID proposal C: outsource this to the editor, e.g. a pumla editor plugin (e.g. for pycharm and VS Code) D: only have the "pumla update" check for alias/ID clashes and report errors