Let's say I have a list of possible resource paths (relative to some file). How would one request the address for the valid ones (tossing the invalid ones?) E.g. If I have

data/foo.json

I know is relative to some dir

./bar

(e.g.

./bar/data.foo.json

), if it's a valid resource I want it's address, otherwise no-op)

Other options: 1. Compute the path you want and then use

Get(Digest, PathGlobs(…))

to attempt to make a

Digest

out of files from the repo. 2. Require that the resource file be the subject of a `resource`target and then use `DependenciesRequest`to get the deps and then just find the resource target in the returned

Dependencies

and load it via its

Sources

field (i.e., with

HydratesSourcesRequest

or equivalent).

Wondering if I should make another flavor of this that returns an Optional and doesn’t raise 

ResolveError

I think this would be useful to have. For the Docker backend, when using heuristics to determine possible dependencies, it would be good to have a rule to apply that gives you back any valid addresses, and discards the invalid ones without err.

@curved-television-6568 I guess I'd still need to verify the addresses are resources...

Then you should just be able to convert to

Targets

and scan for whatever targets has the

resource

-specific sources field.

I might need some hand-holding on this one 😅 . But AFAICT I need to take my string, and reference it against the global set of all resource targets? If so, I think I'm on the right track...