As discussed @softwareplumber, the diagram generation code is overkill currently, with more code written than generated. With more diagrams that could change, and I've had thoughts about the instrumentation code being gen'd as well in a way that didn't require keeping it in sync with non-instrumented code, but totally fair point and that's clearly not on the critical path, and arguably of little value as the code base settles down.
The main reason I'm reverting this code is today's realization that you aren't using the Makefile, such that the use of go generated packages complicates your workflow. No worries. I learned about go generate and some code parsing stuff anyway. :)
As discussed @softwareplumber, the diagram generation code is overkill currently, with more code written than generated. With more diagrams that could change, and I've had thoughts about the instrumentation code being gen'd as well in a way that didn't require keeping it in sync with non-instrumented code, but totally fair point and that's clearly not on the critical path, and arguably of little value as the code base settles down.
The main reason I'm reverting this code is today's realization that you aren't using the Makefile, such that the use of go generated packages complicates your workflow. No worries. I learned about go generate and some code parsing stuff anyway. :)