DrMarkusVoss
commented
3 years ago Create
- pumla_project_config.puml (copy of pumla_global_cfg.puml, to have project-specific settings instead of tool-installation-specific settings)
- create a pumla_blacklist.txt (empty)
Then execute init step
Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like The workflow that will be created with #9 addresses the usage of pumla with an existing repository where pumla artifacts already exist. Another workflow would be needed to setup a project from scratch with pumla. There also the init would need to be called, but additionally also e.g. the pumla_blacklist.txt and pumla_prj_cfg.puml can be setup as first version. The new "pumla_macros.puml" that will then be stored in the project root folder, will also include "pumla_prj_cfg.puml" from the project repo. The current "pumla_global_cfg.puml" could then be used as template, the file itself will not anymore be included by other ".puml" files.
Additional context This shall only be implemented after issue #9 is solved, because the concepts of these two need to be aligned.