Skip the templatedata.go intermediate step

[coryan]

sidekick parses Protobuf or OpenAPI (and whatever comes next) and creates a api.API model of the service specification.

Then we ask the target language Codec (currently for Rust or Go) a bunch of questions and create the model in templatedata.go. And then we use the same mustache templates that the Codec creates to generate the code.

Maybe a cleaner approach would be to pass the api.API model directly to the Codec and let it call the mustache templates. The Codec can create its own enriched¹ model of the API if needed.

@dangazineu suggested the good parts of this issue request, the bad ideas came from somebody else (not me, of course).

Footnotes

1. I think that is what the cool kids call them. ↩