(GH-10459) Reorganize grouping expression docs #10461
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
Prior to this change, the documentation for using grouped expressions in _about_Operators_ included two subheadings: 1. Grouping assignment statements 1. Piping grouped expressions However, it also defined a third use-case for grouping, which showed how to use the grouping operator to use the output of a command in an expression. This use case was documented before the subheadings and after a sentence indicating there's ways to use the grouping operator beyond overriding operator precedence. Further, the section for grouping assignment statements was very long compared to the other use-cases and placed in the middle, despite being less commonly used than the others. This change: - Adds a subheading for the first use case to make it equivalent to the others in the information hierarchy. - Moves the section for piping grouped expressions to before the section for grouping assignment statements. - Resolves MicrosoftDocs#10459 - Fixes AB#163845
Contributor
|
Learn Build status updates of commit d59288d: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
sdwheeler
previously approved these changes
Sep 26, 2023
reference/5.1/Microsoft.PowerShell.Core/About/about_Operators.md
Outdated
Show resolved
Hide resolved
Contributor
|
Learn Build status updates of commit 2becb46: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Contributor
|
🙏 |
michaeltlombardi
deleted the
ab-163845/main/grouping-operator-restructure
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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
Prior to this change, the documentation for using grouped expressions in about_Operators included two subheadings:
However, it also defined a third use-case for grouping, which showed how to use the grouping operator to use the output of a command in an expression. This use case was documented before the subheadings and after a sentence indicating there's ways to use the grouping operator beyond overriding operator precedence.
Further, the section for grouping assignment statements was very long compared to the other use-cases and placed in the middle, despite being less commonly used than the others.
This change:
about_Operatorstopic #10459PR Checklist