Fix Get-ChildItem -Path with wildcard char#7403
Fix Get-ChildItem -Path with wildcard char#7403kwkam wants to merge 1 commit intoPowerShell:masterfrom
Conversation
Unescape non-literal, non-glob path before existence checking. This solve the issue where Get-GhildItem does not behave correctly when -Path contains special characters. For example, > Get-ChildItem -Path './`[dir`]' will complain with error "Cannot find path ..." while > Get-ChildItem -Path './`[dir`]' -Depth 0 will work fine.
kwkam
changed the title
|
This PR has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed if no further activity occurs within 10 days. |
|
This PR has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed if no further activity occurs within 10 days. |
|
This PR has be automatically close because it is stale. If you wish to continue working on the PR, please first update the PR, then reopen it. |
|
It seems that I cannot reopen this. Do I have to create a new PR? |
|
@kwkam I believe if you submit a new commit to this branch it should allow you to reopen it / reopen automatically. |
|
@vexx32 I have merged the latest master into this branch, but still there is no option for re-opening the PR. Maybe I do not have the permission to reopen my PR? |
|
That's very strange... I guess you can just open a new PR from the same branch? |
2 participants
PR Summary
Unescape non-literal, non-glob path before existence checking.
This solve the issue where Get-GhildItem does not behave correctly
when -Path contains special characters. For example,
will complain with error "Cannot find path ..." while
will work fine.
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:to the beginning of the title and remove the prefix when the PR is ready.[feature]if the change is significant or affects feature tests