We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new_project.kts
RFC: #268
When running new_project.kts, it runs a series of steps to generate a new project.
Let's say one of the steps failed, then the new project folder is currently not removed.
This gives the user the wrong impression that the generated project is safe to use.
force=true
README.md
helpMessage
Users of the template will be less confused in case the project generation failed.
The text was updated successfully, but these errors were encountered:
[#433] Add force argument
8ec8185
[#433] Delete generated project on error if forceProjectCreation is f…
221a012
…alse
15301ff
fccb703
[#433] Update README with force argument
2939d2e
Merge pull request #469 from nimblehq/chore/433-remove-new-project-fo…
53958f2
…lder-if-new_projectkts-fails [#433] Remove new project folder if `new_project.kts` fails
ryan-conway
Successfully merging a pull request may close this issue.
RFC: #268
Why
When running
new_project.kts
, it runs a series of steps to generate a new project.Let's say one of the steps failed, then the new project folder is currently not removed.
This gives the user the wrong impression that the generated project is safe to use.
Acceptance Criteria
force=true
(false by default), to optionally force the generation even though there's an error.README.md
&helpMessage
insidenew_project.kts
Who Benefits?
Users of the template will be less confused in case the project generation failed.
The text was updated successfully, but these errors were encountered: