Open ghost opened 4 years ago
The one issue that arises from having one update file per generator version is that you can execute the update only once per generator release which is rather restricting.
A suggestion would be to have one file per generator version which contains steps. In the repo is saved apart from the generator version the step number. (con: could be error prone since the developer might add the wrong step id to a step) Maybe having the steps in an array and execute them depending on the index (con: you can then only append to the steps, you cannot insert freely in any index)
Maybe have a file for each update would be simpler (con: still error prone, perhaps leaving the update template generation to the generator itself makes it less error prone)
Because we have a lot of repos, we should have the possibility to auto-update the repos; therefore we need the following:
new Generator - auto-update:
prName
)utils/autoUpdate
with the parameter:baseType
,generatorVersion
,generatorDirectory
prName
with the givenassignees
and push it to GitHubutils/autoUpdate(baseType, generatorVersion, generatorDirectory)
version
of local generator version from .yo-rc.json file (localVersion
)version
field in the .yo-rc.json (localVersion = generatorVersion - 1
)while (localVersion < generatorVersion)
:localVersion
update-<localVersion>.js
update<localVersion>.js
file with the following parameters:repoDirectory (root), baseType
localVersion
to .yo-rc.json