peczenyj / GDPR-IAB-TCFv2 / 25491282391

95%

main: 96%

Pull #62

github

chore(cli): remove --json-array; default JSONL output is enough

Removes the --json-array flag from both `iabtcfv2 dump` and
`iabtcfv2 validate`.  The default JSON Lines output (one JSON
object per line) is the universal format -- every text-processing
tool reads it directly, and `jq -s .` wraps it into a single
JSON array when callers actually need that shape.

Carrying --json-array meant carrying state-tracking code in both
subcommands: opening/closing brackets gated on quiet/text/fail-fast
combinations, comma-injection between records, the dead `_indent`
helper, plus a mutually-exclusive check between --text and
--json-array in validate.  All of that goes; the per-record print
now reduces to `print $j->encode($data) . "\n"`.

Migration: replace `iabtcfv2 dump --json-array ...` with
`iabtcfv2 dump ... | jq -s .` (or any equivalent JSONL-to-array
tool).  POD examples updated to show the jq pipeline.

Test plan:
  - t/10-cli-iabtcfv2.t: dropped the --json-array functional test;
    replaced with a JSONL-shape assertion (multiple TC strings ->
    multiple newline-separated JSON objects).
  - help-text assertion for --json-array dropped; replaced with
    --pretty.
  - Full suite passes (16536 tests; xt/critic and xt/tidy green).

This is technically a breaking CLI change three commits after
v0.370 shipped, but the migration path is one shell pipe.  Worth
the simplification.

3 of 3 new or added lines in 1 file covered. (100.0%)

897 of 942 relevant lines covered (95.22%)

12386.56 hits per line