Hey @hundreds-father-404! Funny story! Internally at Twitter we have a goal called

scalafix

which does the equivalent to your

--fmt --fmt-only=scalafix

proposed flag! I know this because when you added the

Scalafix

subsystem, and took the option scope, we started getting errors 😄 How sad would you be if I added a v1

--fmt-only

flag which only accepts not being set, or accepts exactly

scalafix

(i.e. not do the fully general solution) to help us with migration?

Totally fine with me! As stated in the google doc, it’s not in my near time roadmap to implement

—fmt-only

. My main goal was to deprecate

—fmt-skip

and that’s now done. (My next project for my free time is the Flake8 plugin so that we can deprecate the checker)

afaik,

--fmt-only

could maybe live on the

v2

fmt Goal, and be consumed by

v1

Yes, it can!

true. note to selves, consider accelerating these deprecations.

afaik,

--fmt-only

could maybe live on the

v2

fmt Goal, and be consumed by

v1

Ooh fancy!

but see above re deprecation =/ ... unless it went on the mixin in the interim, which would work but be strange.

true. note to selves, consider accelerating these deprecations.

This problem is why I’m trying to get as many deprecations going now as possible, so that we’re not blocked by similar things in the future I’ll email pants-commiters about our discussion last week to slightly speed up deprecations

It could go in the mixin exactly until it moves to v2 - would be transparent?

Yes, I think that works fine! Fmt2 won’t have the functionality but that’s fine for now

#CreativeSolutions

there is a minor wart with doing it on the mixin (could do something like

--fmt-scalafix-only=..

) but i would be fine with that briefly appearing and then disappearing at the end of this deprecation cycle

Oh yeah the mixin gets applied to both the goal and the tasks...I don’t think the mixin would work?

it would, i think... would just have the wart above.

I’ll see what I can hack together 🙂

Uh could you do something like an if statement to check if options scope == fmt and if not, don’t register the new option? Horribly hacky but it’s going away soon

Yeah, I’ll hack something 🙂

sooo, @average-vr-56795: what ended up being the conclusion here? looks like this is an issue in the nightly... is the idea to deprecate/remove the goal and suggest

./pants fmt --only=scalafix

instead?

Ooh, I totally didn’t implement that, did I?

thanks. it sounds like toolchain are going to lead the

1.25.x

release next week, so i'll need to raise this on the rc threads.