loud-laptop-1794912/14/2021, 7:03 PM
run only on BUILD files which have changed? In pre-commit and CI I would like to avoid checking every file if we can.
hundreds-father-40412/14/2021, 7:10 PM
is semi-blocked by this proposal https://docs.google.com/document/d/1WWQM-X6kHoSCKwItqf61NiKFWNSlpnTC5QNu3ul9RDk/edit#heading=h.1h4j0d5mazhu
which is the change I most want to make in 2022
loud-laptop-1794912/14/2021, 7:50 PM
eager-dress-6640512/14/2021, 8:05 PM
the only way to get our build files formatted? Can/should
apply to build files? It seems like "update the syntax of all build files for the latest version of pants" is a deeper and broader task than "format recently update BUILD files"
witty-crayon-2278612/14/2021, 8:20 PM
eager-dress-6640512/14/2021, 11:23 PM
currently runs both types of formatters (black and pyupgrade), but the later might get split into a
goal in a later version,
is the only currently available way to format
files be it for indentation or new pants syntax?
+1 for making the
be able to run lightweight formatting (e.g. black) on `BUILD`files.
hundreds-father-40412/14/2021, 11:27 PM
is currently the only way to do it
The first step I want to do is unify
. I realized it's not very valuable for them to be separate. My dream is that you can run
(fusion of both) and it will make sure all your Pants config is in tip-top shape. Any missing targets are added, deprecations are fixed, BUILD files are pretty
./pants --changed-since=HEAD update-pants-config
witty-crayon-2278612/15/2021, 12:10 AM
making semantic changes to BUILD files, pants config, python files, scala files, etc, etc
making formatting changes to all of the above.