Now that the schema changes for `fmt` and `lint` a...
# development
b
Now that the schema changes for
fmt
and
lint
are in, I thought I share a bit of my personal roadmap for upcoming features: • Add
fix
, which is identical to
fmt
in implementation ◦ Move the
experimental
tools there, non-experimental • Make a "rule maker" helper for the default partitioning of these goals • Reduce plugin boilerplate for the result types of these goals (no need to plumb the input/name) • (Maybe) Introduce a copyright targetless-formatter 🙂 • (Maybe) Introduce a useful "meta" plugin to run
fix
as
fmt
(or vice-versa)
👍 2
🙌 1
w
nice.
thanks a lot for summarizing that: it’s really useful… would be great if we all did it more often.
❤️ 2
👍 2
fwiw: i really, really think that https://github.com/pantsbuild/pants/issues/16967 has legs, and wish that i had time to work on it myself.
b
We'd need to still be able to partition by other means, like a directory for terraform or config for scala
w
yea: that would be computed metadata about a file.
👍 1
Fields (“typed metadata about a Target”) were/are a really powerful concept, and https://github.com/pantsbuild/pants/issues/16967 is really about taking that further… “typed, computed metadata about a file”
c
I feel that aligns in a way with what I’m looking for with synthetic targets.. perhaps could be re-worked into being even more so..?
w
@curved-television-6568: yes, i think it really does! i didn’t want to ping you because i haven’t read your document yet, sorry =/
(i’ll summarize my todo list too)
c
great, then I’m on the right mind-track. no worries about the read through. I realize you have to prioritize and I’m not going to push/question that 🙂
❤️ 1
b
Oh I forgot to add: • Maybe dream up a pants.toml deprecations fixer • Use that to start moving to plugin tailor options