PowerShell Community Call Notes for Dec. 08, 2016 (Audio recording here)
- Rejecting RFC0011 on the basis that people can have folders full of scripts that begin with a number
- Accepting RFC0012 for SSH parameter sets, but we should generally fix the parameter set problem:
- Kirk is willing to take on an RFC for better Formatting and Output of
Get-Command -Syntax - We should also close on the RFC for mutually exclusive parameter sets
- Kirk is willing to take on an RFC for better Formatting and Output of
- #2290: Add Get-FileEncoding cmdlet or function.
- Generally agree that
Get-FileEncodingandConvertFrom-FileEncodingwould be useful, especially as we move to a cross-plat world (PowerShell on Linux, Bash on Windows, etc) - Kirk points out that it would be useful to have this functionality downlevel, and so putting it in Utility might be undesirable
- Generally agree that
- #1103: PowerShell Scripts require .ps1 extension
- Without any regard for perf, we probably want to allow no extension AND a shebang
- HOWEVER,
Get-Commandwill probably slow down due to having to open every file with a+xflag. - Current POR: Remove the requirement for a file extension and see how the perf impacts Get-Command and tab completion.
- #621: Fix Remove-Item
- Committee agrees that removing a symbolic link should not require
-Force - We should also fix the bug in 5.1 where the link doesn't ever get removed
Remove-Itemshould never remove the contents of a link's target when removing the link (even w/-Forceor-Recurse)
- Committee agrees that removing a symbolic link should not require
- #2820: Empty key name converting to PSObject
- Given the improvements being made to the Utility module, it would be useful to have those changes on downlevel versions of PowerShell (kind of like how we ship Archive today)