If I wanted to get the more "pure" representation of what a backend's dependency inference is doing, would that be

filedeps

and/or

--transitive

?

what do you mean "pure"?

I'm not sure exactly. Like, whatever the closest representation is to the output of

UnionRule(InferDependenciesRequest, InferCCDependenciesRequest)

We have

dependencies

which works on targets it looks like, then

filedeps

as well. My underlying thing here is that in some cases, I was thinking about seeding dependency inference with some extra information based on targets or options - but I'm not sure if that would be reflected in the goals. So, from step 1, just trying to figure out which introspection API I should concern myself with

dependencies are always from the perspective of targets. You can use

./pants peek path/to:tgt

to compare the raw declared deps vs the final set of deps

So, what's the difference between

filedeps

(List all source and BUILD files a target depends on.) and `dependencies`(List the dependencies of the input files/targets.)?

filedeps

gets the sources of the deps. it ignores targets w/o files, and dedupes when multiple targets have the same sources. It also adds in the BUILD file where the target is defined

Ah okay, thanks!