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
currently we are "suffering" from this bug #103
I was wondering why this fix did not apply to our setup and did some investigations...
We are using the swagger-codegen-maven-plugin having the library option configured to spring.
The SpringCodegen class is still using Mustache as template engine.
// todo: remove this once handlebar templates for this generator are implemented@OverrideprotectedvoidsetTemplateEngine() {
templateEngine = newMustacheTemplateEngine(this);
}
I would really like to take the fix into our spring codegen setup and I am willing to migrate/help migrating but I am not sure what is left to do to migrate spring code gen from mustache templates to handlebars.
The text was updated successfully, but these errors were encountered:
I am running in this bug #103 as well . I was wondering if there's any way to choose which template engine to use through some configuration or settings?
Hi,
currently we are "suffering" from this bug #103
I was wondering why this fix did not apply to our setup and did some investigations...
We are using the swagger-codegen-maven-plugin having the library option configured to
spring
.The SpringCodegen class is still using Mustache as template engine.
It looks like the templates have already been migrated. At least there are template in the handlebar folder https://github.com/swagger-api/swagger-codegen-generators/tree/master/src/main/resources/handlebars/JavaSpring
I would really like to take the fix into our spring codegen setup and I am willing to migrate/help migrating but I am not sure what is left to do to migrate spring code gen from mustache templates to handlebars.
The text was updated successfully, but these errors were encountered: