Add more information about 'using' scope modifier #5596
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Docs Build status updates of commit c31496f:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md | View (powershell-5.1) | Details | |
| reference/5.1/Microsoft.PowerShell.Core/About/about_Scopes.md | View (powershell-5.1) | Details | |
| reference/6/Microsoft.PowerShell.Core/About/about_Remote_Variables.md | View (powershell-6) | Details | |
| reference/6/Microsoft.PowerShell.Core/About/about_Scopes.md | View (powershell-6) | Details | |
| reference/7.0/Microsoft.PowerShell.Core/About/about_Remote_Variables.md | View (powershell-7) | Details | |
| reference/7.0/Microsoft.PowerShell.Core/About/about_Scopes.md | View (powershell-7) | Details | |
| reference/7.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md | View (powershell-7.x) | Details | |
| reference/7.1/Microsoft.PowerShell.Core/About/about_Scopes.md | View (powershell-7.x) | Details |
reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/5.1/Microsoft.PowerShell.Core/About/about_Scopes.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning. - Line 220: [Warning]
Invalid file link:(~/5.1/ThreadJob/Start-ThreadJob.md).
reference/6/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/6/Microsoft.PowerShell.Core/About/about_Scopes.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/7.0/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/7.0/Microsoft.PowerShell.Core/About/about_Scopes.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/7.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/7.1/Microsoft.PowerShell.Core/About/about_Scopes.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.
mklement0
reviewed
Mar 14, 2020
mklement0
reviewed
Mar 14, 2020
reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
Outdated
Show resolved
Hide resolved
mklement0
reviewed
Mar 14, 2020
reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
Outdated
Show resolved
Hide resolved
mklement0
reviewed
Mar 14, 2020
mklement0
reviewed
Mar 14, 2020
reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
Outdated
Show resolved
Hide resolved
mklement0
reviewed
Mar 14, 2020
| Remotely executed commands and background jobs run out-of-process. PowerShell | ||
| uses XML-based serialization and deserialization to make the values of | ||
| variables available across the process boundaries. The serialization process | ||
| converts objects to a **PSObject** type. The **PSObject** is general type that |
There was a problem hiding this comment.
I suggest avoiding mentioning of PSObject altogether, because it should be considered an invisible helper type.
The type that matters from a user's perspective is System.Management.Automation.PSCustomObject. While, regrettably, deserialized objects truly are System.Management.Automation.PSObject instances, "luckily" [pscustomobject] refers to System.Management.Automation.PSObject as well (as does [psobject]), so I suggest using [pscustomobject].
Also, the passage is an oversimplification: there is a fixed number of well-known types that do deserialize as their original type; to quote from https://stackoverflow.com/a/59180367/45375:
"
This deserialization maintains type fidelity only for a limited set of known types, as specified in MS-PSRP, the PowerShell Remoting Protocol Specification. That is, only instances of a fixed set of types are deserialized as their original type.
Instances of all other types are emulated: list-like types become [System.Collections.ArrayList] instances, dictionary types become [hasthable] instances, and other types become method-less (properties-only) custom objects ([pscustomobject] instances), whose .pstypenames property contains the original type name prefixed with Deserialized. (e.g., Deserialized.System.Data.DataTable), as well as the equally prefixed names of the type's base types (inheritance hierarchy).
"
There was a problem hiding this comment.
What types maintain fidelity? I cannot find it listed in MS-PSRP.
There was a problem hiding this comment.
I think mentioning PSObjects is fine here. But we should mention that some objects are rehydrated back to their original types (but of course not the original instance). We can mention a few types as examples, but don't need to list them all. But here is the list (note that rehydrated cert types do not include private key):
|
Thank you for taking this further ❤️ |
Jawz84
reviewed
Mar 14, 2020
PaulHigin
suggested changes
Mar 16, 2020
reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
Outdated
Show resolved
Hide resolved
reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
Outdated
Show resolved
Hide resolved
|
Docs Build status updates of commit b7ee86b:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md | View (powershell-5.1) | Details | |
| reference/5.1/Microsoft.PowerShell.Core/About/about_Scopes.md | View (powershell-5.1) | Details | |
| reference/6/Microsoft.PowerShell.Core/About/about_Remote_Variables.md | View (powershell-6) | Details | |
| reference/6/Microsoft.PowerShell.Core/About/about_Scopes.md | View (powershell-6) | Details | |
| reference/7.0/Microsoft.PowerShell.Core/About/about_Remote_Variables.md | View (powershell-7) | Details | |
| reference/7.0/Microsoft.PowerShell.Core/About/about_Scopes.md | View (powershell-7) | Details | |
| reference/7.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md | View (powershell-7.x) | Details | |
| reference/7.1/Microsoft.PowerShell.Core/About/about_Scopes.md | View (powershell-7.x) | Details |
reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/5.1/Microsoft.PowerShell.Core/About/about_Scopes.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning. - Line 220: [Warning]
Invalid file link:(~/5.1/ThreadJob/Start-ThreadJob.md).
reference/6/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/6/Microsoft.PowerShell.Core/About/about_Scopes.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/7.0/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/7.0/Microsoft.PowerShell.Core/About/about_Scopes.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/7.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/7.1/Microsoft.PowerShell.Core/About/about_Scopes.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.
PaulHigin
suggested changes
Mar 17, 2020
| serialization process converts objects to a general type that contains the | ||
| original objects properties but not its methods. | ||
|
|
||
| Deserialization maintains type fidelity only for a limited set of known types. |
There was a problem hiding this comment.
I personally find this more confusing. It is fine to state that arbitrary deserialized types have 'deserialized' in their type name, but I liked the PSObject/property bag explanation. I don't know what 'type emulation' is.
|
Docs Build status updates of commit bcaf6fa:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md | View (powershell-5.1) | Details | |
| reference/5.1/Microsoft.PowerShell.Core/About/about_Scopes.md | View (powershell-5.1) | Details | |
| reference/6/Microsoft.PowerShell.Core/About/about_Remote_Variables.md | View (powershell-6) | Details | |
| reference/6/Microsoft.PowerShell.Core/About/about_Scopes.md | View (powershell-6) | Details | |
| reference/7.0/Microsoft.PowerShell.Core/About/about_Remote_Variables.md | View (powershell-7) | Details | |
| reference/7.0/Microsoft.PowerShell.Core/About/about_Scopes.md | View (powershell-7) | Details | |
| reference/7.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md | View (powershell-7.x) | Details | |
| reference/7.1/Microsoft.PowerShell.Core/About/about_Scopes.md | View (powershell-7.x) | Details |
reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/5.1/Microsoft.PowerShell.Core/About/about_Scopes.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning. - Line 220: [Warning]
Invalid file link:(~/5.1/ThreadJob/Start-ThreadJob.md).
reference/6/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/6/Microsoft.PowerShell.Core/About/about_Scopes.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/7.0/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/7.0/Microsoft.PowerShell.Core/About/about_Scopes.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/7.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/7.1/Microsoft.PowerShell.Core/About/about_Scopes.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.
|
Docs Build status updates of commit c9f5b06:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md | View (powershell-5.1) | Details | |
| reference/5.1/Microsoft.PowerShell.Core/About/about_Scopes.md | View (powershell-5.1) | Details | |
| reference/6/Microsoft.PowerShell.Core/About/about_Remote_Variables.md | View (powershell-6) | Details | |
| reference/6/Microsoft.PowerShell.Core/About/about_Scopes.md | View (powershell-6) | Details | |
| reference/7.0/Microsoft.PowerShell.Core/About/about_Remote_Variables.md | View (powershell-7) | Details | |
| reference/7.0/Microsoft.PowerShell.Core/About/about_Scopes.md | View (powershell-7) | Details | |
| reference/7.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md | View (powershell-7.x) | Details | |
| reference/7.1/Microsoft.PowerShell.Core/About/about_Scopes.md | View (powershell-7.x) | Details |
reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/5.1/Microsoft.PowerShell.Core/About/about_Scopes.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning. - Line 220: [Warning]
Invalid file link:(~/5.1/ThreadJob/Start-ThreadJob.md).
reference/6/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/6/Microsoft.PowerShell.Core/About/about_Scopes.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/7.0/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/7.0/Microsoft.PowerShell.Core/About/about_Scopes.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/7.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/7.1/Microsoft.PowerShell.Core/About/about_Scopes.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.
sdwheeler
changed the title
PaulHigin
suggested changes
Mar 18, 2020
| original objects properties but not its methods. | ||
|
|
||
| For a limited set of types, deserialization rehydrates objects back to the | ||
| original type. The rehydrated object contains the properties but not the |
There was a problem hiding this comment.
This isn't quite right. I'm not sure the right way to explain, maybe:
'The rehydrated object is of the same type as the original object, and is not a PSObject type. It has the type properties and methods, but is a copy of the original object instance. For simple types, such as System.Version, the copy can be exact. For complex types the copy will be imperfect, such as certificates where the copy does not include the private key.'
|
Docs Build status updates of commit 03c7340:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md | View (powershell-5.1) | Details | |
| reference/5.1/Microsoft.PowerShell.Core/About/about_Scopes.md | View (powershell-5.1) | Details | |
| reference/6/Microsoft.PowerShell.Core/About/about_Remote_Variables.md | View (powershell-6) | Details | |
| reference/6/Microsoft.PowerShell.Core/About/about_Scopes.md | View (powershell-6) | Details | |
| reference/7.0/Microsoft.PowerShell.Core/About/about_Remote_Variables.md | View (powershell-7) | Details | |
| reference/7.0/Microsoft.PowerShell.Core/About/about_Scopes.md | View (powershell-7) | Details | |
| reference/7.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md | View (powershell-7.x) | Details | |
| reference/7.1/Microsoft.PowerShell.Core/About/about_Scopes.md | View (powershell-7.x) | Details |
reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/5.1/Microsoft.PowerShell.Core/About/about_Scopes.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning. - Line 220: [Warning]
Invalid file link:(~/5.1/ThreadJob/Start-ThreadJob.md).
reference/6/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/6/Microsoft.PowerShell.Core/About/about_Scopes.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/7.0/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/7.0/Microsoft.PowerShell.Core/About/about_Scopes.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/7.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
reference/7.1/Microsoft.PowerShell.Core/About/about_Scopes.md
- [Warning]
Metadata with following name(s) are not allowed to be set in Yaml header, or as file level metadata in docfx.json, or as global metadata in docfx.json: locale. They are generated by Docs platform, so the values set in these 3 places will be ignored. Please remove them from all 3 places to resolve the warning.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.
This was referenced Mar 19, 2020
This was
linked to
issues
Mar 23, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
Replaces PR #5497 - I had to close this PR because the branch was too stale.
Fixes #5068
@PaulHigin @Jawz84 @mklement0 I made some changes based on the feedback. Let me know how this looks.
PR Context
Select the type(s) of documents being changed.
Cmdlet reference & about_ topics
Conceptual articles
PR Checklist
WIP:or[ WIP ]to the beginning of thetitle and remove the prefix when the PR is ready.