Make some 7.3 Experimental Feature Stable

Summary of the new feature / enhancement

The current ExperimentalFeatures in 7.3:

Name                                Enabled Source                              Description
----                                ------- ------                              -----------
PSAMSIMethodInvocationLogging          True PSEngine                            Provides AMSI notification of .NET method invocations.
PSAnsiRenderingFileInfo                True PSEngine                            Enable coloring for FileInfo objects
PSCleanBlock                           True PSEngine                            Add support of a 'Clean' block to functions and script cmdlets for easy resou…
PSCommandNotFoundSuggestion            True PSEngine                            Recommend potential commands based on fuzzy search on a CommandNotFoundExcept…
PSExec                                 True PSEngine                            Add 'exec' built-in command on Linux and macOS
PSLoadAssemblyFromNativeCode           True PSEngine                            Expose an API to allow assembly loading from native code
PSNativeCommandArgumentPassing         True PSEngine                            Use ArgumentList when invoking a native command
PSNativeCommandErrorActionPreferen…    True PSEngine                            Native commands with non-zero exit codes issue errors according to $ErrorActi…
PSRemotingSSHTransportErrorHandling    True PSEngine                            Removes the SSH remoting transport stdErr stream message handling as terminat…
PSStrictModeAssignment                 True PSEngine                            Add support of setting Strict-Mode with Invoke-Command
PSSubsystemPluginModel                 True PSEngine                            A plugin model for registering and un-registering PowerShell subsystems

Proposed technical implementation details (optional)

Current discussion within the PS-Committee is not complete, but so far we’ve decided:

Make stable:

PSAMSIMethodInvocationLogging - confirm with AMSI team that the API is done and public PSAnsiRenderingFileInfo - make stable to get more user feedback. Since the decoration is user configurable, users can turn it off completely or adjust. The main criteria here is to enable this capability and less about the default colors which are user configurable. We appreciate the feedback (although would have liked it to come earlier) and agreed that since formatting changes are not breaking changes, we should proceed with the current defaults and we can continue discussing with the community potential changes for the defaults in 7.4 previews. PSCleanBlock - an opt-in feature that’s been available for awhile and commit to fixing bugs should they come up PSExec - provide consistency with expectations on non-Windows platforms PSNativeCommandArgumentPassing - we’ve received good feedback on this which greatly improves the experience on non-Windows and Windows specific issues have been addressed, we agreed to take this for 7.3 and continue to address issues into 7.4 as needed PSRemotingSSHTransportErrorHandling - this addresses a major issue with SSH remoting where native command use stderr as information and not an error which previously would kill the connection, so we want to take this fix

Keep Experimental:

PSCommandNotFoundSuggestion - pending on rewrite of Suggestion framework to make it work correctly PSLoadAssemblyFromNativeCode - keep as experimental to see if there are more users that want/need this type of feature PSNativeCommandErrorActionPreference - keep as experimental as we don’t have any data if users have used this feature given that it’s opt-in by default, consider making it opt-out in 7.4 PSSubsystemPluginModel - re-discussed within the Committee and agreed to keep this experimental, but support Az.Predictor dependency

Remove as feature:

PSStrictModeAssignment - Remove as feature since it’s not enabled for remoting and is not very useful when limited to local usage

We will review the other ones at next meeting.

[SteveL-MSFT]

@dkaszews color options for MatchInfo would have to be an entirely new feature. Feel free to open a new issue to discuss the idea and would be helpful to have proposal on how it would be exposed to users as well as use cases showing its utility.

[dkaszews]

Ad colors: I’m quite satisfied with the defaults, as they closely match bash. And while we should absolutely not treat “we should be like bash” as the ultimate goal, opening two windows side by side and seeing both directory listings look similar was satisfying. Plus, it allows us to leverage existing user expectations from a well established color design.