2a739afa9c
* Fix Rename-Item to allow Unix globbing patterns in -Literal paths (#2799) In the process of normalizing a relative path, PowerShell checks to see see if the path exists, which it does by invoking Directory.EnumerateFiles(directory, filename); On Unix platforms, if the filename contains globbing patterns, such as [ab], EnumerateFiles (and EnumerateDirectories) will perform the globbing. Using globbing patterns, a file named 'file[txt].txt' is reported as not existing. This fix changes the file-existence test on Unix to use a native function instead of either of the Directory.EnumerateXXX functions. * Fix for AppVeyor failure * Changes per code review, and a couple of letter-casing changes. |
||
|---|---|---|
| .. | ||
| common/markdown | ||
| csharp | ||
| docker/networktest | ||
| fullclr | ||
| powershell | ||
| PSReadLine | ||
| shebang | ||
| tools | ||
| map.json | ||
| README.md | ||
Testing
The tests are organized by testing language. Thus Pester tests, which are written in the PowerShell language, are in ./powershell and xUnit tests, written in C#, are in ./csharp. The sanity tests for the Full .NET build of PowerShell are in ./fullclr, and the third-party shebang test is in ./shebang.