-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
31 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
# Printing JSON in the Shell | ||
|
||
Printing json might seem straightforward at first, just: | ||
|
||
```shell | ||
$ echo '{"name": "jes", "sign": "aquarius"}' | ||
# {"name": "jes", "sign": "aquarius"} | ||
``` | ||
|
||
but inevitably, variables show up: | ||
|
||
```shell | ||
$ echo '{"name": "$name", "sign": "$sign"}' | ||
# {"name": "$name", "sign": "$sign"} <-- this output is very broken | ||
``` | ||
|
||
We can instead use `printf`! `printf` offers several advantages over echo: | ||
|
||
- many languages (C, Go) have a `printf` equivalent, so it feels familiar | ||
- `printf` behavior does not differ across systems (it is posix compliant) | ||
- `printf` handles escape sequences (`printf "hello\nworld\n"`) | ||
- `printf` can trivially handle json | ||
|
||
Printing the same json text using `printf`: | ||
|
||
```shell | ||
$ printf '{"name": "%s", "sign": "%s"}' "$name" "$sign" | ||
# {"name": "jes", "sign": "aquarius"} | ||
``` | ||
|
||
[source](https://j3s.sh/thought/shell-tip-print-json-with-printf.html) |