You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just an idea, but one potential feature that could be really handy is a confirmation step that optionally occurs before the files are written; similar to how npm init does it:
This would give consumers the ability to see what files are going to be generated, and the ability to bail out if they entered something incorrectly OR might accidentally overwrite something they don't intend to. It will add a little transparency to each option and what it does, which can be very reassuring.
This could easily be an opt-in or opt-out feature by adding it to the API:
Just an idea, but one potential feature that could be really handy is a confirmation step that optionally occurs before the files are written; similar to how
npm init
does it:This would give consumers the ability to see what files are going to be generated, and the ability to bail out if they entered something incorrectly OR might accidentally overwrite something they don't intend to. It will add a little transparency to each option and what it does, which can be very reassuring.
This could easily be an opt-in or opt-out feature by adding it to the API:
Are you open to contributions? I am interested in taking a stab at adding this feature, if you agree it is a feature worth pursuing. Thanks!
The text was updated successfully, but these errors were encountered: