meta(output): tracking issue for issues related to output modes (--json, stdout, stderr)

[zerosnacks]

Issues

Flags

• Many flags are incompatible with each other but not marked as such resulting in a hard crash or unexpected output

--json

• bug: forge test --gas-report --json yields unexpected data and misses data #8789
• bug(forge test): JSON output should consistently adhere to verbosity flags #8735
• bug: traces field is missing when display option --json is set #6922
• feat(forge test) add an optional --json-file argument to write both to stdout and to a JSON file #2210
• feat(cast): add an unformatted output mode #6600
• feat(cast): add event-decode command to parsing and formatting log data #6511
• JSON export for flamegraph #8926
• feat(coverage): add --json compatibility to forge coverage --report summary #4071
• feat(cast): add --json flag in cast wallet new-mnemonic #9138
• forge build --sizes is not compatible
• forge build --names is not compatible
• forge build --format-json always prints (even if empty) when combined with other flags
• forge script --json is not clean

stdout, stderr

• bug(cast): failed printing to stdout: Broken pipe (os error 32) #8568
• bug: forge script crash when piping to command that doesn't take stdin: "failed printing to stdout: Broken pipe (os error 32)" #7055
• forge create prints logs to stdout instead of stderr #1976
• indicatif progress bars to do not respect output redirecting #3981
• feat: route all prints through common::shell #6569 (resolves above)
• Allow avoiding passing large arguments through program args #5069

[sakulstra]

I think is not yet referenced here yet, but another command where --json output would be important is build --sizes.

In our CIs we're currently jumping trough hoops to track changes in contract size and gas consumption.