Fixes #7171 - Updates about_CommonParameters + 1 more #7177
Conversation
… formatting for common-parameter-names
|
Docs Build status updates of commit d974acf:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| reference/5.1/Microsoft.PowerShell.Core/About/about_CommonParameters.md | View (powershell-5.1) | Details | |
| reference/7.0/Microsoft.PowerShell.Core/About/about_CommonParameters.md | View (powershell-7) | Details | |
| reference/7.1/Microsoft.PowerShell.Core/About/about_CommonParameters.md | View (powershell-7.1) | Details | |
| reference/docs-conceptual/developer/cmdlet/common-parameter-names.md | ✅Succeeded | View (>=powershell-5.1) |
reference/5.1/Microsoft.PowerShell.Core/About/about_CommonParameters.md
- Line 375, Column 54: [Warning-file-not-found]
Invalid file link: 'about_functions_advanced'.
reference/7.0/Microsoft.PowerShell.Core/About/about_CommonParameters.md
- Line 375, Column 54: [Warning-file-not-found]
Invalid file link: 'about_functions_advanced'.
reference/7.1/Microsoft.PowerShell.Core/About/about_CommonParameters.md
- Line 375, Column 54: [Warning-file-not-found]
Invalid file link: 'about_functions_advanced'.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching in the Docs contributor and Admin Guide
- See the frequently asked questions
- Post your question in the Docs support channel
sdwheeler
left a comment
sdwheeler
left a comment
There was a problem hiding this comment.
See my suggested edits.
| >[!NOTE] | ||
| > When using the **PipelineVariable** parameter with [advanced functions](about_functions_advanced), | ||
| > it will only accept the first value from the function to the pipeline and any | ||
| > others will be ignored. The behavior is corrected in PowerShell 7.2 |
There was a problem hiding this comment.
| >[!NOTE] | |
| > When using the **PipelineVariable** parameter with [advanced functions](about_functions_advanced), | |
| > it will only accept the first value from the function to the pipeline and any | |
| > others will be ignored. The behavior is corrected in PowerShell 7.2 | |
| >[!NOTE] | |
| > When using the **PipelineVariable** parameter with [advanced functions](./about_functions_advanced.md), | |
| > only the first value is assigned to the variable as values flow through the | |
| > pipeline. PowerShell 7.2 corrects this behavior. |
| >[!NOTE] | ||
| > When using the **PipelineVariable** parameter with [advanced functions](about_functions_advanced), | ||
| > it will only accept the first value from the function to the pipeline and any | ||
| > others will be ignored. The behavior is corrected in PowerShell 7.2 | ||
|
|
There was a problem hiding this comment.
| >[!NOTE] | |
| > When using the **PipelineVariable** parameter with [advanced functions](about_functions_advanced), | |
| > it will only accept the first value from the function to the pipeline and any | |
| > others will be ignored. The behavior is corrected in PowerShell 7.2 | |
| >[!NOTE] | |
| > When using the **PipelineVariable** parameter with [advanced functions](./about_functions_advanced.md), | |
| > only the first value is assigned to the variable as values flow through the | |
| > pipeline. PowerShell 7.2 corrects this behavior. |
| >[!NOTE] | ||
| > When using the **PipelineVariable** parameter with [advanced functions](about_functions_advanced), | ||
| > it will only accept the first value from the function to the pipeline and any | ||
| > others will be ignored. The behavior is corrected in PowerShell 7.2 | ||
|
|
There was a problem hiding this comment.
| >[!NOTE] | |
| > When using the **PipelineVariable** parameter with [advanced functions](about_functions_advanced), | |
| > it will only accept the first value from the function to the pipeline and any | |
| > others will be ignored. The behavior is corrected in PowerShell 7.2 | |
| >[!NOTE] | |
| > When using the **PipelineVariable** parameter with [advanced functions](./about_functions_advanced.md), | |
| > only the first value is assigned to the variable as values flow through the | |
| > pipeline. PowerShell 7.2 corrects this behavior. |
reference/docs-conceptual/developer/cmdlet/common-parameter-names.md
Outdated
Show resolved
Hide resolved
|
Docs Build status updates of commit b2382a8:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| reference/5.1/Microsoft.PowerShell.Core/About/about_CommonParameters.md | View (powershell-5.1) | Details | |
| reference/7.0/Microsoft.PowerShell.Core/About/about_CommonParameters.md | View (powershell-7) | Details | |
| reference/7.1/Microsoft.PowerShell.Core/About/about_CommonParameters.md | View (powershell-7.1) | Details | |
| reference/docs-conceptual/developer/cmdlet/common-parameter-names.md | ✅Succeeded | View (>=powershell-5.1) |
reference/5.1/Microsoft.PowerShell.Core/About/about_CommonParameters.md
- Line 375, Column 54: [Warning-file-not-found]
Invalid file link: 'about_functions_advanced'.
reference/7.0/Microsoft.PowerShell.Core/About/about_CommonParameters.md
- Line 375, Column 54: [Warning-file-not-found]
Invalid file link: 'about_functions_advanced'.
reference/7.1/Microsoft.PowerShell.Core/About/about_CommonParameters.md
- Line 375, Column 54: [Warning-file-not-found]
Invalid file link: 'about_functions_advanced'.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching in the Docs contributor and Admin Guide
- See the frequently asked questions
- Post your question in the Docs support channel
Co-authored-by: Sean Wheeler <sean.wheeler@microsoft.com>
|
Docs Build status updates of commit 7d5a153:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| reference/7.0/Microsoft.PowerShell.Core/About/about_CommonParameters.md | View (powershell-7) | Details | |
| reference/7.1/Microsoft.PowerShell.Core/About/about_CommonParameters.md | View (powershell-7.1) | Details | |
| reference/5.1/Microsoft.PowerShell.Core/About/about_CommonParameters.md | ✅Succeeded | View (powershell-5.1) | |
| reference/docs-conceptual/developer/cmdlet/common-parameter-names.md | ✅Succeeded | View (>=powershell-5.1) |
reference/7.0/Microsoft.PowerShell.Core/About/about_CommonParameters.md
- Line 375, Column 54: [Warning-file-not-found]
Invalid file link: 'about_functions_advanced'.
reference/7.1/Microsoft.PowerShell.Core/About/about_CommonParameters.md
- Line 375, Column 54: [Warning-file-not-found]
Invalid file link: 'about_functions_advanced'.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching in the Docs contributor and Admin Guide
- See the frequently asked questions
- Post your question in the Docs support channel
|
Docs Build status updates of commit 593f01b: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
This reverts commit 73708f7.
|
Docs Build status updates of commit 924a964: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
|
Docs Build status updates of commit 4c7f961: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
6 participants
PR Summary
Updates doc versions previous to 7.2 to note the PipelineVariable parameter behavior when used with advanced functions.
PR Context
Fixes #7171
Fixes AB#1810840
Select the area of the Table of Contents containing the documents being changed.
Conceptual content
Cmdlet reference & about_ topics
PR Checklist
WIP:or[WIP]to the beginning of thetitle and remove the prefix when the PR is ready.