https://pantsbuild.org/ logo
Join Slack
Powered by
<@U01PZK60W2F> While this may become moot in a cou...
# development
w
@curved-television-6568 While this may become moot in a couple weeks/months, was there a way to extract the BUILD file where a target is defined, via peek?
c
you can deduce it somewhat reliably off of the target address I believe.. but that’s a bit hacky at best
the code that added the BUILD file source origin for a target is not yet merged. There’s merge conflicts on my PR for that which I’ve begun looking into..
w
you can deduce it somewhat reliably off of the target address I believe
I think that only works in the 111
the code that added the BUILD file source origin for a target is not yet merged.
Ah okay, this is what I had in my head, wasn't sure whether I was rememebring this
c
I think you get 
src/foo/bar/baz.py:../../target-name
in case you have a greedy glob at a root.
where the number of 
../
will be indicative of where the BUILD file is
👀 1
w
where the number of 
../
will be indicative of where the BUILD file is
Oh wow, those were sitting in front of me, and my brain didn't even register the dots 🤯
😄 1
Ah, wait, that’s right - I think I tried using the relative target name in suspenders, but one of the hiccups came from build file naming
DOes the new PR include the file name?
c
yep, the filename is in there. also made a change so the filename is kept separate from the line number for use in peek output
w
Ooooh, line number, you say…. 😋
Would be great to be able to jump straight to the correct target in the build file
👍 1
c
just need that PR 18366 reviewed so we can proceed with the peek changes
w
That’s a hefty PR. I’ll be free to look at some PRs this weekend, but that’s also entirely out of my knowledge base
😁 1
Open in Slack
PreviousNext
Powered by