Allow the template containing directory to be excluded from the output path #32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If the project requires two folders created at the root level `templatePath: ".templates/Example/", outputPath: "."` then we don't want 'Example' being created as a new folder, just the folder contents should be copied.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently when a template is output, the directory within the template directory is automatically added to the output path. This means you can't use it to output templates where the output directory is the root and sub-folders are
./srcand./testfor example.The optional
excludeDirectoryconfig parameter adds the ability to not output the template directory in the output path. Which means the library can be used on a much more diverse set of codebases.