Confusion around how --quiet and --fix should behave together

See #8353 for background.

I think the best way to fix this is to allow users the option to go either way and to be very explicit about how the options work.

Here’s one proposal along those lines:

• Rename --quiet to --no-report-warnings (supporting --quiet as an alias and preserving its behavior), to avoid reporting warnings but possibly fix them
• Add option --no-fix-warnings to support not running autofix on warnings but possibly report them (no effect if --fix not specified)
• Users can use both to completely ignore warnings altogether

With this proposal, our CLI options become more clear and more flexible with regard to whether warnings are reported/logged (--quiet/--no-report-warnings) and whether warnings are fixed (--no-fix-warnings).

I’ll champion.

[mysticatea]

Just arranged. Granted, looks good to me if we change that ※ as a bug.

Option	Error reported	Error fixed	Warning reported	Warning fixed
(default)	✔		✔
--quiet	✔
--fix	✔	✔	✔	✔
--fix --quiet	✔	✔		※

※ Currently, warnings are fixed but not reported.

[platinumazure]

@mysticatea Yes, I think you’re right, that behavior is unexpected (and was the root of the original issue). I like the direction you’re going, but maybe we could bikeshed the name a little bit?

How about this?

• --warnings=report-and-fix (default)
• --warnings=report-only (no fix, but report warnings)
• --warnings=none (don’t report or fix warnings, alias --quiet)