GeezerVison

Is your description in "Before the fix:" correct? It seems #9014 is not fixed jet. Also PowerShell Committee conclusion was to reject the change.

This PR will fix #9014:

PS Q:\yard> Get-ChildItem -Path *.md -Recurse -Name
note.md
.abc\abc.md
delme\delme.md
tmp\hello\world\world.md

PS Q:\> Get-ChildItem -Path Q:\yard\*.md -Recurse -Name
note.md
.abc\abc.md
delme\delme.md
tmp\hello\world\world.md

I didn't know that issue and thanks for pointing me to it.

I disagree with the WG conclusion. It's hard to imagine someone would depend on this breaking behavior -- they specify -Recurse but Get-ChildItem doesn't traverse the directories. I think if there is anyone who is doing that today, it's very likely they didn't know it's broken and assumed it works the way they expected (same as dir -path ... -Recursive but just output the names).

Note that Get-ChildItem -Path . -Include *.md -Recurse -Name works today, and that makes it hard to justify the -Name behavior except for accepting that it's broken. This kind of inconsistency impacts how AI can write high-quality PowerShell commands when using PowerShell as the shell-invocation tool on Windows.

This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days.
Maintainer, please provide feedback and/or mark it as Waiting on Author

This is a breaking change but is not marked as such. It will break patterns i use like renaming a directory to "directory.old", "directory.old.old" etc. It should at least be documented as a breaking change in the release notes.