Ability to disable and suppress all errors but those explicitly enabled

[connernilsen]

Would be awesome to have something where I could tell Pyrefly to disable all errors except what I pass in. Same with doing suppressions. This would make it easier to migrate some projects if I'm focusing on one error at a time, which works well with the way that we can enable/disable by config error.

This could be a big motivator for error profiles (all off, strict, basic/default, ...)

[samwgoldman]

Can you clarify a bit more? What would you "pass in"?

[connernilsen]

I was thinking that we have --include, --exclude, and --warn, which are explicit overrides to error configuration. So in this case, there could be a flag --disable-all, which when combined with --include and --warn, would allow us to turn on specific errors to look at or --suppress.

Even better if --disable-all were something like --error-profile <all|off|strict|basic|...>.

[yangdanny97]

--error-profile <default|all|explicit> for now, perhaps (we'd add strict later).

explicit = "only emit errors explicitly set via --warn or --error"

in terms of implementation, I imagine these would affect the "default severity" for errors, which would apply before any severity overrides from config or CLI.

Once we deicde on the naming for the flags, we should mark this as a "good first issue"

[yangdanny97]

Actually I think we could reuse the --only flag, and make it work like error/warn/info where you can pass multiple error codes

pyrefly/pyrefly/lib/commands/check.rs

Line 239 in 6055447

only: Option<crate::config::error_kind::ErrorKind>,

[rchen152]

#1753 does the CLI piece of this (but doesn't add an equivalent config file option).