[Upgrade-Tool] Refactor the CLI and add codemods commands #19984
Conversation
Convly
added
pr: enhancement
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
|
| @@ -79,7 +79,7 @@ export class Upgrader implements UpgraderInterface { | |||
| `${this.target.major}.${this.target.minor}.${this.target.patch}` | |||
| ); | |||
|
|
|||
| this.logger?.debug( | |||
| this.logger?.debug?.( | |||
There was a problem hiding this comment.
Is there a reason we don't require a logger everywhere? and/or if we don't want one we create a stub that doesn't actually log anything?
There was a problem hiding this comment.
In the future, we might want to programmatically create an upgrader instance that won't log anything (silent).
We could create a stub, but I found it simpler to assume we might not have a logger at all. What do you think?
|
There's a small issue with logging when running multiple codemods with the |
Fixed, thanks! |
|
FYI @Marc-Roig |
…ol/enhance-codemods-command
What does it do?
codemods run [uid]to run codemods (optionally provide a single codemod UID)codemods lsto get a list of available codemodscodemod-runner,codemod-repository,codemod)Why is it needed?
Allow listing available codemods and running specific ones, especially useful when developing codemods for a version that's not available now.
How to test it?
codemods ls,codemods run [UID]) and make sure everything works according to the help description