Support using a glob to find a file and output the file #56
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
|
@gregnb do you have thoughts or opinions on approaching a fix for this? I tried to quickly make the following code change but realize we need a way to glob match files which would require including a package like + // if the destination contains an extension assume it's a file, even if
+ // provided a glob.
+ const isFile = path.extname(command.destination);
- if (matches === null) {
+ if (matches === null || isFile) { |
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.
Resolves #27.
For example, copying
{ source: "./dist/*.js", destination: "./testing/testingglob.js" }should copy the file that matches the glob"./dist/*.js"to"./testing/testingglob.js"but today it copies as a directory with the glob pattern within./testing/testingglob.js/*.js.