Fix the conflict between paths for OutputPath & ArchiveFileName
#65
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
iRebbok
force-pushed
the
fix/conflict_with_outputpath_and_archivefilename
branch
from
8717ebd to
d660e31
Compare
|
Looks good to me. @kborowinski, what do you think? |
|
Version 1.13 has been published to PowerShell Gallery. Thanks for your work! |
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.
@kborowinski mentioned in #63 a conflict between absolute paths in
ArchiveFileName, now this is fixed, and also with relative paths.will create an archive in
C:\TMP.will create an archive in the parent folder of the current folder.
will create an archive in
C:\MyPath.I think this is what completely resolves the conflict between
ArchiveFileName&OutputPath.