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
Given a (new) package name, it should create a directory for that package and initialize a package file from a template. The script can ask for the user to provide additional metadata at the command prompt and give them directions on how to continue writing the package file. We should also have a flag to disable this interactivity and just generate a template file (for users who prefer editing the file directly).
We could add hints or outright force the user to confirm a choice we find not good (like _ in versions or missing -n at the end) without the user needing to read how to make it him/herself. (kinda like npm init or other project creation tools i guess)
The text was updated successfully, but these errors were encountered:
(As proposed by @raisjnn and @LinusCDE on Discord.)
Given a (new) package name, it should create a directory for that package and initialize a package file from a template. The script can ask for the user to provide additional metadata at the command prompt and give them directions on how to continue writing the package file. We should also have a flag to disable this interactivity and just generate a template file (for users who prefer editing the file directly).
Possible scenario:
We could add hints or outright force the user to confirm a choice we find not good (like _ in versions or missing -n at the end) without the user needing to read how to make it him/herself. (kinda like npm init or other project creation tools i guess)
The text was updated successfully, but these errors were encountered: