Expanded examples for foreach alias, loops and keywords #473
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
Added a few examples in AboutLoopsAndPipelines regarding the
foreach
cmdlet alias vs loop and how thebreak
,continue
andreturn
keywords affect pipelines vs standard loops.Fixes #404
Context
No particular context or background for the PR, see issue for linked discussions and examples of topics.
Changes
Added a new
Context
to AboutLoopsAndPipelines called "Loops and Keywords" with 5 newIt
assertions to clarify some important things regarding pipeline loops vs keyword/standard loops.is possible to break a standard loop
- Showsbreak
in a normal loopis possible to skip iterations of a standard loop
- Showscontinue
in a normal loopis possible to return a value from a standard loop
- Showsreturn
in a normal loophas the same name but not the same behaviour
- Showsbreak
with a pipelineforeach
aliasreturns differently when used in a pipeline
- Showsreturn
with a pipelineForEach-Object
Checklist