fix(analyze): respect --log-level in output and JSON

[dreyfus92]

this wires --log-level through to what you actually see: pretty analyze output and the messages array in --json now only include severities at or above the chosen level, so stuff like --log-level error finally hides warnings/suggestions instead of feeling broken. If you still want the full diagnostic list in JSON but need a stricter exit code, there’s --json-full for that. Unknown message severities are treated like warnings so nothing silently disappears.

closes: #192

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@e18e/cli@194

commit: 8078cd1

[43081j]

why do we need this? would we not just set the right log level?

[dreyfus92]

so this is my reasoning, --log-level ties together 2 things: what counts for the exit code and (by def now) what goes in messages. those aren't always the same want --json-full splits them for JSON consumers so you can keep a strict exit policy without throwing away diagnostics. we need it when consumers want the full messages payload but --log-level should only gate CI exit; raising log level to get more messages also changes when we exit non-zero, so this flag decouples those for --json.

[43081j]

i understand now. im not a fan of json-full though 😅

e.g. ESLint has --quiet which means "only output errors"

so maybe we need --output-level or --report-level or something...