#22536 Simplify, or at least properly justify, the lint/fix/fmt request class hierarchy Issue created by benjyw And then document it! Right now it is a confusing mishmash of

Abstract{Lint/Fmt/Fix}Request

, and subclasses of those for each tool, plus a

.Batch

nested class that is distinct for each enclosing class (via a

@distinct_union_type_per_subclass

annotation). And then there are also

{Lint/Fix}{Targets/Files}Request

which are also subclasses of the

Abstract{Lint/Fmt/Fix}Request

types, and these are mixed in odd ways. And then there are also

is_fixer

and

is_formatter

booleans on those types. It's a lot. pantsbuild/pants