On Sat, Apr 25, 2026 at 06:12:13PM -0700, Joe Perches wrote:
On Sat, 2026-04-25 at 20:07 -0400, Sasha Levin wrote:
On Sat, Apr 25, 2026 at 02:52:35PM -0700, Joe Perches wrote:
On 2026-04-25 13:04, Sasha Levin wrote:
Add a --json flag to checkpatch.pl that emits structured JSON output,
> > making results machine-parseable for CI systems, IDE integrations, and
> > AI-assisted code review tools.
> []
> > A separate --json-pretty flag emits the same JSON in a pretty-printed
> > (indented, multi-line) form for human reading
> Why not just always use pretty?
> Would a script care?
Who's the intended consumer for the --json-pretty?
I my mind, --json is there to make it easier for tooling to process the output.
Agree, but does the pretty output make it harder for tooling?
For real JSON parsers, no - they handle either form fine.
The one issue is multi-file invocations: --json emits one compact document per
file per line (NDJSON), which lets plain-shell consumers do `while read line;
do ...` or pipe through grep/awk/head. Pretty mode loses that property because
each document spans multiple lines, so consumers need a
streaming JSON parser.
--
Thanks,
Sasha
