You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the same way we can generate multiple operation files from a single template, it would be beneficial to generate multiple model files from a single template. This would allow us to support strongly typed languages that share interfaces/models.
We'd just need a way to differentiate those types of files. Currently, operations are denoted by three underscores, maybe we could reserve some other set of characters for models. Another idea to solve for this would be to have some kind of file registry. This would allow us to associate a template explicitly with one of the many ways it can be interpreted by the codegen. This would also let us name handlebar files in .hbs so we can get some intellisense while templating locally.
I'd be happy to work on this :)
The text was updated successfully, but these errors were encountered:
In the same way we can generate multiple operation files from a single template, it would be beneficial to generate multiple model files from a single template. This would allow us to support strongly typed languages that share interfaces/models.
We'd just need a way to differentiate those types of files. Currently, operations are denoted by three underscores, maybe we could reserve some other set of characters for models. Another idea to solve for this would be to have some kind of file registry. This would allow us to associate a template explicitly with one of the many ways it can be interpreted by the codegen. This would also let us name handlebar files in
.hbs
so we can get some intellisense while templating locally.I'd be happy to work on this :)
The text was updated successfully, but these errors were encountered: