The current solution for SwiftGen proposed in #37 uses the default template provided by the tool, which might change according to the version. This might be a problem since we currently have no way of enforcing a specific SwiftGen version for the generation of the required asset files.
A possible solution for that is the creation of a custom stencil template shared across all modules, which also enables us to meet certain needs of modularization and have more control over the resulting files to make further improvements.
The current solution for SwiftGen proposed in #37 uses the default template provided by the tool, which might change according to the version. This might be a problem since we currently have no way of enforcing a specific SwiftGen version for the generation of the required asset files.
A possible solution for that is the creation of a custom stencil template shared across all modules, which also enables us to meet certain needs of modularization and have more control over the resulting files to make further improvements.