Workaround Powershell 6.2/7.0 breaking compatibility with Get-ChildItem #8013
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
Powershell 6.2/7.0 in infinite wisdom decided to change the value of what `Get-ChildItem` (and anything dealing with FileInfo/DirectoryInfo) returns from relative to absolute path. The only way to work around this for both existing versions and future versions is to explicitly request the `Name`. Hopefully this doesn't get changed again. NOTE: This PS change breaks a lot of scripts, including many of Microsoft's own first-party scripts. No workarounds were pushed for any that I could see in the year+ since the issue was first reported.
|
This looks good to me, and is more correct. Thanks @TheGoddessInari I'm going to modify the commit message, though. |
strega-nil
pushed a commit
that referenced
this pull request
Sep 6, 2019
In Powershell 6.2/7.0, `Get-ChildItem`'s paths are now printed as absolute paths instead of relative paths; this breaks the code we have that assumes that they're printed as relative paths. Thus, change the code to request the `Name` property specifically, which is what we actually wanted.
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.
Powershell 6.2/7.0 in infinite wisdom decided to change the value of
what
Get-ChildItem(and anything dealing with FileInfo/DirectoryInfo)returns from relative to absolute path.
The only way to work around this for both existing versions and future
versions is to explicitly request the
Name. Hopefully this doesn'tget changed again.
NOTE: This PS change breaks a lot of scripts, including many
of Microsoft's own first-party scripts. No workarounds were pushed
for any that I could see in the year+ since the issue was first
reported.