❗ I just opened a GitHub Discussion I'd love for the community to chime in on, as it is quite pervasive to our modeling of targets and dependencies. ❗ https://github.com/pantsbuild/pants/discussions/15847 TL;DR one "untyped" dependencies field is certain succinct and ideal, but is starting to show cracks under the weight of the unique use-cases we want to throw at it. So where do we go from here?

Is there any way to add examples (like, contrived real-life-ish use cases) of how this would look? I'm trying to envision this in a project, and am coming up blank (maybe because I haven't had my coffee today)

The little toy code-snippets are meant to help the brain-juices with examples, but are admittedly trim. I'm weary of drowning the meat of the prose in codeblocks 😕

In a comment maybe'?

Look again?

Grokking very well now 🙂

I'm +1 to the general idea of

dependencies

having multiple named fields that make it more clear what's happening. I don't like right now how

dependencies

is unclear and not intuitive what will happen

Can you comment on the discussion so I can reply over there? Also plz specify which numeric option you're referring to 😛

Added my $0.02 CAD... After conversion to USD and rounded up - well, probably still my 2 cents

OK Last chance to add comments before I take the feedback and start work on a proposal