Code generation - what are our options?

[JonruAlveus]

We’re talking a lot about code gen and I thought it would be good to kick off a chat about it.

So far I’ve successfully generated a postman collection (not really related to this Repo but it was pretty easy). I also unsuccessfully generated a c# client using the ms open api connected service. There is one endpoint with one enum that accepted add, Add, remove, Remove etc. which exploded because you ended up with two enums with the same name, but different values. Doh. So I guess we could ask to change the documentation to only show upper or lower or we find a different tool.

Another thing to consider is extending the generated code with the undocumented endpoints (repos/owner/name is there but repos/id or repository/id aren’t).

Other options could be handlebars or liquid templates to build own own entirely or there must be others out there. I guess we could also consider doctoring the open api json ourselves to make it fit to our need?

[JamieMagee]

I think a Roslyn source generator¹ would be the best way to build the client. The only one I know of is H.NSwag.Generator²

Footnotes

1. https://docs.microsoft.com/en-us/dotnet/csharp/roslyn-sdk/source-generators-overview ↩

2. https://github.com/HavenDV/H.NSwag.Generator ↩

[nickfloyd]

@JonruAlveus Would you mind if we move this to a discussion? Not a big deal, but I'd like to start driving many more conversations that way so we can benefit from the features of the discussions toolset and keep our issues tidy... I'd be glad to move it over if you want.

[JonruAlveus]

@nickfloyd Sure! Are you able to convert it into a discussion? According to the docs there's a button on the right to convert it automatically. If not, I'll do a copy and paste job :)