denali upgrade, when run inside a Denali app or addon, should upgrade to the specified (latest by default) version of Denali. This includes updating package.json and installing the version, but also running any kind of blueprint necessary to update any app structures or files.
An open question:
Do we simply run a blueprint again and, a la ember-cli, give the user the option to accept the change? Or do we try to do something more sophisticated as well/instead? For example, ship Denali itself with migration scripts, something more like codemod.
(moved from https://github.com/denali-js/denali/issues/181, see there for additional comments)
denali upgrade
, when run inside a Denali app or addon, should upgrade to the specified (latest by default) version of Denali. This includes updating package.json and installing the version, but also running any kind of blueprint necessary to update any app structures or files.An open question:
Do we simply run a blueprint again and, a la ember-cli, give the user the option to accept the change? Or do we try to do something more sophisticated as well/instead? For example, ship Denali itself with migration scripts, something more like codemod.