Anyone have opinions on per-target kob on ignore/warn/error of unmatched source(s) glob?

Can't you tweak the globs to not fail the match?

I don't follow?

Why do you have an unmatched source glob to begin with?

Because the files may or may not exist on disk. 🙂 These files are produced programmatically, and not in a way we can have Pants do it for us. So for most people, they don't exist. And for the few who care, they do

I see

Hehe we do in other places, but no. That means we'd dirty a file tracked by

git

😉

Could be a separate

BUILD.generated

file that is gitignored?

Sure, but now we're severely engineering around Pants 😐

Yes, but this is a very specific case

Fair 🙂

What about something like

~path/to/file.py

meaning that the file need not exist

Ehhh I'm not a fan of symbolic syntax. (See the visibility rules 😛 )

That seems to require a lot less new plumbing

Let's see what others say as far as if this is rare or not, and go from there 🙂

Yeah but I'm not a fan of added complexity, so meet me half way here

It might be I'm in the minority, so we do nothing 🙂

From the issue comment I posted, I have an idea about flagging a value as being “default” so it doesn’t warn/error on unmatched globs. There are a few different ways how to get that that I can think of.. either it could be the thing it does when set using

__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.