:cry: Everything was looking so neat. The tool we...
# random
a
😢 Everything was looking so neat. The tool we're using references other dependencies in arbitrary files using some arbitrary string-interpolation syntax. I was just using pants address specs, but in one file type they use a different parser and it didn't match the
:target
portion of the spec. I've had to go and do
target.address.spec.replace(':', '.')
in my plugins. so close. yet so far.
h
What's the context here?
a
the stupid runtime envrionment our code runs in has some awful configuration thing. Where
&{A_THING}
gets referenced in a lookup table of
A_THING: THE_ACTUAL_THING
So I'm wrapping this with Pants, and making it so that
A_THING
is the address spec e.g.
path/to:a_thing
Then hopefully, in the future, doing inference so I don't even need to add
path/to:a_thing
in the targets dependencies. Except in one case, where it doesn't detect the
:a_thing
. So I have to transform everything to
path/to.a_thing
and it looks stupid and is dumb.
If there's interest, Once it's running, and we're using it daily, I'm going to request permission from our media dept to write an article for the pants blog. The environment is a product of one of pants' competitors 😆
💯 1
❤️ 2
h
we love sharing case studies. so useful for other teams. that'd be great!