Allow skipping errors
Opened this issue · 1 comments
When developing a new codemod, it would be helpful to be able to allow continuing regardless of exceptions with some sort of debug flag or parameter passed to runInteractiveCodemodSequence.
Something like
--continue-on-exceptions
Motivation: It's hard to catch every edge case when creating a migration when there are a lot of breaking changes like what happened recently with package riverpod going to v1.0.0-dev. Users would still like to be able to do a best-effort migration when the migration tool has exceptions, so that they don't have to do the full migration manually and don't have to wait for the migration tool to be flawless.
A CLI flag like --continue-on-exceptions makes sense, especially for automated use cases where they might be using --yes-to-all as well. Seems like we could also update the default behavior of runInteractiveCodemodSequence to catch these exceptions and prompt the user on whether they want to continue or quit.