-
The use case would be to describe models, then emit JSON Schema and matching TS/C# classes, but without necessarily detailing an API. The C# classes would emit JSON compatible with the emitted Schema. In related discussions, codegen seems to imply HTTP clients, so I figured this is a bit separate. The intended result would be transport agnostic interop c# types and JSON Schema. Is that already possible, planned or out of scope? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
It is definitely possible to define only models in a tsp spec and then use the various language emitters to emit those as classes / interfaces in their respective languages without defining any services or operations in your tsp. |
Beta Was this translation helpful? Give feedback.
-
Thanks a lot, that's what I wanted to know! |
Beta Was this translation helpful? Give feedback.
It is definitely possible to define only models in a tsp spec and then use the various language emitters to emit those as classes / interfaces in their respective languages without defining any services or operations in your tsp.