Textrude VS NTypewriter

Fair point - source generators can run arbitrary code so yes, they can read a json file and then spit out something else in response. If you want to translate the json schema into the equivalent C# you'll need to write a small amount of code to deserialize the json into a JObject tree, walk it, and emit c# code. I do something similar in my Textrude code-generation/templating project except I'm translating the tree into an equivalent Scriban object tree. The relevant source code is here. All that said, this is a fairly specialised and common task - I can't believe there's not a command line tool to do this already.

Plug for something I wrote: [github link]*https://github.com/NeilMacMullen/Textrude). The CLI version can pipe json (or yaml,csv or text lines) from stdin or fetch it from a URL then turn it into model and apply a Scriban template to it to emit text to stdout. Runs on Linux or Windows and also comes with an interactive UI prototyping tool.

I am currently using NTypewriter for code generation.

With NTypewriter you can generate anything. It connects Scriban templates with data exposed from Roslyn API. You can run templates from VS (design time) or embed them (run time) into your application with the help of Buildalayzer.

With NTypewriter you can generate clients for any language (TS, Java), because you have full control over generated code, but similar to other tools, it uses C# as an input language.

You can use NTypewriter for that, it is mainly for generating typed TS clients, but in general, you can generate whatever you want.

You can try to use NTypewriter for code generation, but its main purpose is generation of java script clients for APIs or documentation.

NTypewriter is better and alive, but I am definitely biased.