Funny thought: why is our dep parser internal? Why...
# development
b
Funny thought: why is our dep parser internal? Why not publish it like another tool?
w
in general: public APIs have a higher maintenance burden than private APIs
1
even if the publishing was fully automated and transparent, you’d still potentially have to worry about the API you were providing to non-Pants consumers
b
I think it has a lot of value though, there's a few other tools in the same space. Since our API amounts to simply dumping JSON I wouldn't be extremely worried about breaking compatibility
It also encourages plugins/extensions easier, since we're headed that direction
And I'm kinda thinking a little bit of "rewrite it in rust"
w
Since our API amounts to simply dumping JSON I wouldn’t be extremely worried about breaking compatibility
Benjy needed to break compatibility recently, iirc
but yea, i’m down with rewrite-it-in-rust. just not sure that that needs to necessarily be coupled to a decision to publish it as a separate tool.
b
Returning different JSON could be behind a feature flag
Either way. Both directions are possible