Thinking about dissolving

update-build-files

, where should the plugin be located?

pants.backend.build_files

? (We have global options which use the term "build_file") We might able to do something a la: •

pants.backend.build_files.fmt.black

and

pants.backend.build_files.fmt.isort

? •

pants.backend.build_files.fix.upgrader

?

I think a precursor question is: should the functionality always be activated? Or you must explicitly opt into the backend?

I don't think it should always be activated. I don't run

update-build-files

today because I format my files with a custom formatter and until PR it, I can't turn off the existing formatting 🙂

That sounds wise to have it be opt-in. Or at a minimum let you opt-out

Alternatively we could have formatting be plugin-based?

s/like//

build files are code files

In this care they aren't code files, they don't have an associated field set