Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add more information about 'using' scope modifier #5596

Merged

Conversation

@sdwheeler
Copy link
Contributor

sdwheeler commented Mar 14, 2020

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

  • Version 7.x preview content
  • Version 7.0 content
  • Version 6 content
  • Version 5.1 content

Conceptual articles

  • Fundamental conceptual articles
  • Script sample articles
  • DSC articles
  • Gallery articles
  • JEA articles
  • WMF articles
  • SDK articles

PR Checklist

  • I have read the contributors guide and followed the style and process guidelines
  • PR has a meaningful title
  • PR is targeted at the staging branch
  • All relevant versions updated
  • Includes content related to issues and PRs - see Closing issues using keywords.
  • This PR is ready to merge and is not Work in Progress
    • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the
      title and remove the prefix when the PR is ready.
@sdwheeler sdwheeler requested a review from PaulHigin Mar 14, 2020
@opbld31

This comment has been minimized.

Copy link

opbld31 commented Mar 14, 2020

Docs Build status updates of commit c31496f:

⚠️ Validation status: warnings

File Status Preview URL Details
reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md ⚠️Warning View (powershell-5.1) Details
reference/5.1/Microsoft.PowerShell.Core/About/about_Scopes.md ⚠️Warning View (powershell-5.1) Details
reference/6/Microsoft.PowerShell.Core/About/about_Remote_Variables.md ⚠️Warning View (powershell-6) Details
reference/6/Microsoft.PowerShell.Core/About/about_Scopes.md ⚠️Warning View (powershell-6) Details
reference/7.0/Microsoft.PowerShell.Core/About/about_Remote_Variables.md ⚠️Warning View (powershell-7) Details
reference/7.0/Microsoft.PowerShell.Core/About/about_Scopes.md ⚠️Warning View (powershell-7) Details
reference/7.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md ⚠️Warning View (powershell-7.x) Details
reference/7.1/Microsoft.PowerShell.Core/About/about_Scopes.md ⚠️Warning 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.

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

This comment has been minimized.

Copy link
@mklement0

mklement0 Mar 14, 2020

Contributor

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).
"

This comment has been minimized.

Copy link
@sdwheeler

sdwheeler Mar 17, 2020

Author Contributor

What types maintain fidelity? I cannot find it listed in MS-PSRP.

This comment has been minimized.

Copy link
@PaulHigin

PaulHigin Mar 17, 2020

Contributor

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):

https://github.com/PowerShell/PowerShell/blob/master/src/System.Management.Automation/engine/serialization.cs#L6609

@Jawz84

This comment has been minimized.

Copy link
Contributor

Jawz84 commented Mar 14, 2020

Thank you for taking this further ❤️

@sdwheeler sdwheeler force-pushed the sdwheeler:5068_remote_variables_using branch from c31496f to b7ee86b Mar 17, 2020
@opbld32

This comment has been minimized.

Copy link
Member

opbld32 commented Mar 17, 2020

Docs Build status updates of commit b7ee86b:

⚠️ Validation status: warnings

File Status Preview URL Details
reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md ⚠️Warning View (powershell-5.1) Details
reference/5.1/Microsoft.PowerShell.Core/About/about_Scopes.md ⚠️Warning View (powershell-5.1) Details
reference/6/Microsoft.PowerShell.Core/About/about_Remote_Variables.md ⚠️Warning View (powershell-6) Details
reference/6/Microsoft.PowerShell.Core/About/about_Scopes.md ⚠️Warning View (powershell-6) Details
reference/7.0/Microsoft.PowerShell.Core/About/about_Remote_Variables.md ⚠️Warning View (powershell-7) Details
reference/7.0/Microsoft.PowerShell.Core/About/about_Scopes.md ⚠️Warning View (powershell-7) Details
reference/7.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md ⚠️Warning View (powershell-7.x) Details
reference/7.1/Microsoft.PowerShell.Core/About/about_Scopes.md ⚠️Warning 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.

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.

This comment has been minimized.

Copy link
@PaulHigin

PaulHigin Mar 17, 2020

Contributor

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.

https://github.com/PowerShell/PowerShell/blob/master/src/System.Management.Automation/engine/serialization.cs#L6609

@sdwheeler sdwheeler force-pushed the sdwheeler:5068_remote_variables_using branch from bcaf6fa to c9f5b06 Mar 18, 2020
@opbld31

This comment has been minimized.

Copy link

opbld31 commented Mar 18, 2020

Docs Build status updates of commit bcaf6fa:

⚠️ Validation status: warnings

File Status Preview URL Details
reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md ⚠️Warning View (powershell-5.1) Details
reference/5.1/Microsoft.PowerShell.Core/About/about_Scopes.md ⚠️Warning View (powershell-5.1) Details
reference/6/Microsoft.PowerShell.Core/About/about_Remote_Variables.md ⚠️Warning View (powershell-6) Details
reference/6/Microsoft.PowerShell.Core/About/about_Scopes.md ⚠️Warning View (powershell-6) Details
reference/7.0/Microsoft.PowerShell.Core/About/about_Remote_Variables.md ⚠️Warning View (powershell-7) Details
reference/7.0/Microsoft.PowerShell.Core/About/about_Scopes.md ⚠️Warning View (powershell-7) Details
reference/7.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md ⚠️Warning View (powershell-7.x) Details
reference/7.1/Microsoft.PowerShell.Core/About/about_Scopes.md ⚠️Warning 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.

@opbld34

This comment has been minimized.

Copy link
Member

opbld34 commented Mar 18, 2020

Docs Build status updates of commit c9f5b06:

⚠️ Validation status: warnings

File Status Preview URL Details
reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md ⚠️Warning View (powershell-5.1) Details
reference/5.1/Microsoft.PowerShell.Core/About/about_Scopes.md ⚠️Warning View (powershell-5.1) Details
reference/6/Microsoft.PowerShell.Core/About/about_Remote_Variables.md ⚠️Warning View (powershell-6) Details
reference/6/Microsoft.PowerShell.Core/About/about_Scopes.md ⚠️Warning View (powershell-6) Details
reference/7.0/Microsoft.PowerShell.Core/About/about_Remote_Variables.md ⚠️Warning View (powershell-7) Details
reference/7.0/Microsoft.PowerShell.Core/About/about_Scopes.md ⚠️Warning View (powershell-7) Details
reference/7.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md ⚠️Warning View (powershell-7.x) Details
reference/7.1/Microsoft.PowerShell.Core/About/about_Scopes.md ⚠️Warning 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 sdwheeler changed the title WIP: add more information about 'using' scope modifier Add more information about 'using' scope modifier 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

This comment has been minimized.

Copy link
@PaulHigin

PaulHigin Mar 18, 2020

Contributor

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.'

@opbld33

This comment has been minimized.

Copy link
Member

opbld33 commented Mar 18, 2020

Docs Build status updates of commit 03c7340:

⚠️ Validation status: warnings

File Status Preview URL Details
reference/5.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md ⚠️Warning View (powershell-5.1) Details
reference/5.1/Microsoft.PowerShell.Core/About/about_Scopes.md ⚠️Warning View (powershell-5.1) Details
reference/6/Microsoft.PowerShell.Core/About/about_Remote_Variables.md ⚠️Warning View (powershell-6) Details
reference/6/Microsoft.PowerShell.Core/About/about_Scopes.md ⚠️Warning View (powershell-6) Details
reference/7.0/Microsoft.PowerShell.Core/About/about_Remote_Variables.md ⚠️Warning View (powershell-7) Details
reference/7.0/Microsoft.PowerShell.Core/About/about_Scopes.md ⚠️Warning View (powershell-7) Details
reference/7.1/Microsoft.PowerShell.Core/About/about_Remote_Variables.md ⚠️Warning View (powershell-7.x) Details
reference/7.1/Microsoft.PowerShell.Core/About/about_Scopes.md ⚠️Warning 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.

Copy link
Contributor

PaulHigin left a comment

LGTM

@sdwheeler sdwheeler merged commit 7e4c963 into MicrosoftDocs:staging Mar 18, 2020
3 checks passed
3 checks passed
OpenPublishing.Build Validation status: warnings
Details
PowerShell-Docs-CI #PR-5596-20200318.03 succeeded
Details
license/cla All CLA requirements met.
Details
@sdwheeler sdwheeler deleted the sdwheeler:5068_remote_variables_using branch Mar 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.