Skip to content

Fix Get-Runspace runspace object format Type column#9438

Merged
adityapatwardhan merged 3 commits intoPowerShell:masterfrom
PaulHigin:fix-runspace-format-type
May 1, 2019
Merged

Fix Get-Runspace runspace object format Type column#9438
adityapatwardhan merged 3 commits intoPowerShell:masterfrom
PaulHigin:fix-runspace-format-type

Conversation

@PaulHigin
Copy link
Copy Markdown
Contributor

This addresses issue #9341.

Any runspace that uses a RunspaceConnectionInfo object is a remote (proxy) runspace, and should be marked 'Remote' instead of 'Local'. Currently only WSMan runspaces are marked 'Remote', and this change fixes that.

PR Checklist

@adityapatwardhan
Copy link
Copy Markdown
Member

@PaulHigin Is it possible to add a test?

@PaulHigin
Copy link
Copy Markdown
Contributor Author

Since we didn't have a test for this before, I would argue that we don't need to add one now. I think in general we don't test formatted output, but only that formatting and output work functionally.

@TravisEz13 TravisEz13 added this to the 7.0.0-preview.1 milestone Apr 23, 2019
@TravisEz13 TravisEz13 added the CL-General Indicates that a PR should be marked as a general cmdlet change in the Change Log label Apr 23, 2019
@adityapatwardhan adityapatwardhan merged commit aeb6018 into PowerShell:master May 1, 2019
@PaulHigin PaulHigin deleted the fix-runspace-format-type branch July 17, 2019 23:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CL-General Indicates that a PR should be marked as a general cmdlet change in the Change Log

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants