Add destination directory as argument to swift package init
#7792
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #7791
This allows for specifying the directory to create a new package within. If no argument is supplied, matching the current supported command options, then the package will be created in the current working directory. If an argument is supplied, then the package will be created in the directory at the path specified.
Motivation:
The goal is to make the creation of new packages more predictable based on the arguments passed in, as well as to give more control to developers to specify the location of new packages, rather than relying on current working directory contexts and forcing the developer to
mkdir
andcd
a bunch while using this command.Modifications:
swift package init
to take in the directory to create the package atprint
statements during creation to specify the relative directories that the package is being created inResult:
swift package init
is unchanged, where if no arguments are specified, the package will be created in the current working directory.