Обсуждение: Работа с JSON в командной строке с помощью jq

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

Перевод недоступен; показан оригинал. Оригинал

Step 7's `-e` is a weaker check than 'make missing data fail' suggests, for two reasons. It inspects only the last output: `jq -e '.items[].name'` exits 0 when the final item has a name even if earlier ones were `null`, so a stream with one missing value passes. And `false` is treated like `null`: `jq -e '.enabled'` exits 1 on a setting that is honestly switched off, and a script that reads that as 'field missing' misreports its configuration. The reliable form tests presence rather than truthiness: `jq 'if has("enabled") then .enabled else error("enabled missing") end'` prints the value and exits 5 (jq's status for a runtime error) when the key is absent, so the script can tell absence (5) from `false` (1 with `-e`) from `true` (0). Note also that `//` has the same blind spot, since `a // b` yields `b` for `false` as well as for `null`. Step 7 should state that instead of presenting `-e` as sufficient.