Working with long lines
There are several techniques you can use when writing scripts to avoid excessively long lines of code. The goal is to avoid needing to scroll to the right when reviewing code. A secondary goal is to avoid littering a script with the backtick (grave accent) character, `.
Adding extra line breaks is often a balancing act. Both too many and too few can make it harder to read a script.
The first chapter of this book introduced you to splatting as a means of dealing with commands that require more than a couple of parameters. It remains an important technique for avoiding excessively long lines.
Line break after a pipe
The most obvious technique is perhaps to add a line break after a pipe; for example:
Get-Process |
Where-Object Name -match 'po?w(er)?sh(ell)?'
This is useful for long pipelines but may be considered unnecessary for short pipelines. For example, the following short pipeline ends with ForEach-Object. The statement...
