<p><pre><code> > Take for example this one-liner:
> [program listing...]
> In this condensed program of 4 lines, the following happens:
</code></pre>
Right a "one" liner I see...<p>once it gets above roughly 100 characters you are no longer allowed to call it a "one liner"<p>and style note putting the pipe"|" at the end of the command instead of the beginning acts as a natural break and lets you avoid the backslash escaped newline nonsense.<p><pre><code> curl ... |
jq ... |
awk ....
</code></pre>
vs<p><pre><code> curl ... \
| jq ... \
| awk ...</code></pre>
Many of us are no doubt just waiting for the webmaster of www.example.com to realize that there's a marvellous Bobby Tables SQL injection exploit in there. (-:<p>Being a good neighbour involves a bit more than reading from standard input and being about to send JSON to standard output; and there's more to be said about the field parsing, including that fields must not contain interior whitespace, for which vis(1) encoding is a good idea.