Closed skulptur closed 4 years ago
In my opinion we shouldn't add dependencies if we happen to use them often but they are otherwise unrelated to Muban. This way users of Muban are free to pick whatever 'generator-like tooling' they prefer. In my view:
sg
globally.sg
commands that are tailored to your project, rather than having a generic sg wizard
everywhere.Just my personal opinion. I'm open to alternative suggestions.
I get your point and I personally use other tools to generate code in my own projects. However since Muban already comes with the templates for seng generator it seems like a disconnect to not include the tool to make those templates work.
Ah I didn't realize that Muban already comes with templates. In that case I agree with you that does seem like a bit of a disconnect. It might even be a good idea to add a specific version as dependency from a technical standpoint, just in case sg ever gets a major upgrade with a breaking change that's incompatible with the templates in Muban
Currently we're asking devs to install seng generator globaly. This can be inconvenient when setting up new machines or when we need to code in other machines. We should consider adding seng generator as a dependency and adding a new script to the package.json, for example:
"generate": "sg wizard"
.