bitter-ability-32190
05/15/2023, 3:56 PMerror
at $work but we have 2 places where the build process is bootstrapped outside of Pants and ad-hoc (we can't move it into Pants either).
So instead of erroring, we warn and silence those 2 warnings. But that means more warnings pop up and people just ignore them.happy-kitchen-89482
05/15/2023, 4:07 PMbitter-ability-32190
05/15/2023, 4:08 PMhappy-kitchen-89482
05/15/2023, 4:09 PMbitter-ability-32190
05/15/2023, 4:10 PMhappy-kitchen-89482
05/15/2023, 4:11 PMbitter-ability-32190
05/15/2023, 4:12 PMgit
😉happy-kitchen-89482
05/15/2023, 4:13 PMBUILD.generated
file that is gitignored?bitter-ability-32190
05/15/2023, 4:14 PMhappy-kitchen-89482
05/15/2023, 4:15 PMbitter-ability-32190
05/15/2023, 4:16 PMhappy-kitchen-89482
05/15/2023, 4:16 PM~path/to/file.py
meaning that the file need not existbitter-ability-32190
05/15/2023, 4:16 PMhappy-kitchen-89482
05/15/2023, 4:16 PMbitter-ability-32190
05/15/2023, 4:17 PMhappy-kitchen-89482
05/15/2023, 4:17 PMbitter-ability-32190
05/15/2023, 4:18 PMcurved-television-6568
05/15/2023, 5:05 PM__defaults__
or maybe with a sources=default([…])
to indicate the value should be treated as a default value.. I also did think of Benjy’s idea to mark inidividual globs as optional, but that covers another use case than what I had in mind (could be used, but would be awkward). My use case is to re-use/augment the default set of globs for a targets sources value, having to mark each individual glob optional in that case would be a bit janky.