I’m writing a plugin in which I need to run a program (could be Scala, Python or Go) which lives in the same repo. It will produce a metadata file which I then need to do further processing with (run a bunch of validations, so essentially a check goal). I’m wondering what the best pattern is? I could make my field set accept a target which can be packaged, and then execute the packaged binary conditionally (depending on what language it is) and grabbing its output. Or is it better to treat it as some sort of codegen where the output is the generated file, and then have language specific targets which can compile a binary, run it and then output codegen’d files?

Grug brain solution:

shunit2_test

+

adhoc_tool

.

Don’t know, haven’t tried, that could work great! 😀

I think adhoc_tool to generate the output and then any test target for analysis is a reasonable approach in that case.

I went with sort of an in-between solution, using

adhoc_tool

to run the task for the output & a plugin that calls into an npm tool to do the validation. Works great as soon as I figured out how to get the generated sources into my plugin