Closed GarretWayne closed 1 year ago
that is supported already. Except the hardcoded base classes which is a single resource. But every generated class/enum can be generated as separate file
--outputType <OneClassPerFile|SingleFile> Specifies generated classes organization [default: SingleFile]
It also gives you option to have own extensions of the classes using own partial
classes stored anywhere but within the same namespace
Thanks, I will try it out later :)
you can also override/implement GenerationContext
and write your own custom structure.
Based on the classes, interfaces and generated regions it would be great to have a separate file structure, so that we can quickly replace the changed code when we regenerate the client. This could also lead to a better VSC history, as it won't be a megalithic file.