When for example you create a new flynt project via flynt create and you answered all the prompts it could happen, that the flynt create script runs into an issue. This will stop the script and print a list of commands that were not executed due to the issue.
After resolving the issue, I have to either run all these commands manually and hope everything works fine or I have to rerun the whole flynt create script which also asks me for the prompt answers again which gets frustrating if you have more than 1 issue to fix/test
Fix?
I thought about a command, for example flynt continue which allows the user to continue a broken task (for example a new project creation) where the last script stopped working. This way you don't have to run all flynt create xyz commands again and you don't need to reanswer all the prompts.
When does this come handy?
When for example you create a new flynt project via
flynt createand you answered all the prompts it could happen, that theflynt createscript runs into an issue. This will stop the script and print a list of commands that were not executed due to the issue.After resolving the issue, I have to either run all these commands manually and hope everything works fine or I have to rerun the whole
flynt createscript which also asks me for the prompt answers again which gets frustrating if you have more than 1 issue to fix/testFix?
I thought about a command, for example
flynt continuewhich allows the user to continue a broken task (for example a new project creation) where the last script stopped working. This way you don't have to run allflynt create xyzcommands again and you don't need to reanswer all the prompts.