At a project, there's a case where a user wants to use Damascus as a service generator of their custom templates. In that case, users repeat a cycle to generate codes and fix templates accordingly. A functionally to assist the cycle efficiency will be beneficial not only for users but also Damascus contributors as well.
The idea of implementation
Replacement patterns
The default replacement patterns between template value and Keywords (model names, package names and directory names) should be generated in base.json file as optional fields at damascus -init command called.
The fields should be customizable as users may want to add custom patterns as well.
Motivation
At a project, there's a case where a user wants to use Damascus as a service generator of their custom templates. In that case, users repeat a cycle to generate codes and fix templates accordingly. A functionally to assist the cycle efficiency will be beneficial not only for users but also Damascus contributors as well.
The idea of implementation
Replacement patterns
The default replacement patterns between template value and Keywords (model names, package names and directory names) should be generated in base.json file as optional fields at
damascus -init
command called.The fields should be customizable as users may want to add custom patterns as well.