Make S.M.A.PowerShell.GetSteppablePipeline method public #8055
Conversation
|
Similar to the other PR I submitted earlier, I did not include test fixtures for this PR because I was not sure it needed any. If you want some added, please indicate where (Pester, or in a C# unit test). Thank you. |
iSazonov
added
the
Review - Committee
|
Note: after this PR or #8056 are approved/merged, the other will have to be updated with the latest code and the Pester test that tests tab expansion and counts members on S.M.A.PowerShell will have to be updated (the count will increase by one). Just adding this comment so that I remember to update whichever of these isn't merged once the other one is so that there are no merge conflicts and all tests pass. |
|
@PowerShell/powershell-committee reviewed this and is ok making this public |
SteveL-MSFT
added
Committee-Reviewed
|
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 is not stale, it's just awaiting merge. |
TravisEz13
added
the
CL-Engine
5 participants
PR Summary
PowerShell advanced function authors can create proxy functions in native PowerShell, but PowerShell cmdlet authors cannot create proxy cmdlets in native .NET. The S.M.A.PowerShell.GetSteppablePipeline() method is marked as internal, yet it is useful in both PowerShell and .NET when you want to work with proxy commands. This PR is simply to change the visibility of the GetSteppablePipeline method to public so that binary cmdlet authors don't need to use reflection to get access to this essential method.
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