I think that ideally we could make the upgrade just npx elm-review --template gampleman/core-extra/upgrade/template --fix.
Apart from fixing all the deprecations, this should report if the project still depends on any of the elm-community packages core-extra is replacing, as well as if core-extra is not in the dependencies. I don't think this needs an auto fix, we could just tell the users what elm-json command to run...
Ideally the rule would be made that adding simple deprecations (i.e. renames) would be easy, so contributors can do that straightforwardly as part of the PRs actually creating deprecations.
If anyone wants to give this a shot, let's coordinate so we don't duplicate too much effort.
I think that ideally we could make the upgrade just
npx elm-review --template gampleman/core-extra/upgrade/template --fix.Apart from fixing all the deprecations, this should report if the project still depends on any of the elm-community packages core-extra is replacing, as well as if
core-extrais not in the dependencies. I don't think this needs an auto fix, we could just tell the users what elm-json command to run...Ideally the rule would be made that adding simple deprecations (i.e. renames) would be easy, so contributors can do that straightforwardly as part of the PRs actually creating deprecations.
If anyone wants to give this a shot, let's coordinate so we don't duplicate too much effort.