export android studio project as template

Our generators implement a combination of language and framework features, and it's fully possible to use an existing generator to implement a custom template for a different framework. This approach is often the easiest when creating a custom template. OpenAPI Generator supports user-defined templates. Beginning with version 4.0.0, we support experimental Handlebars and user-defined template engines via plugins. OpenAPI Generator applies user-defined templates via options:īuilt-in templates are written in Mustache and processed by jmustache. Take a look at the various implementations as a guideline while the instructions get more complete. The transform logic needs to implement CodegenConfig.java and is most easily done by extending DefaultCodegen.java.

You may need to refer to the generator implementation to understand some of the logic while creating or customizing templates (see ScalaFinchServerCodegen.java for an advanced example). While generators do not need to perform transformations, it's often necessary in order to add more advanced support for your language or framework. This model is then applied to the templates. The generator workflow has transforming logic as well as templates for each generation of code.Įach generator will create a data structure from the OpenAPI document OpenAPI 2.0 and OpenAPI 3.x documents are normalized into the same API model within the generator. Be sure to start here first, because templating is the easier concept and you'll need it for more advanced use cases. If you need to include additional files in your generated output, manipulate the OpenAPI document inputs, or implement your own vendor extensions or other logic, you'll want to read customization after you read this document. It's easy to work with templates for codegen!įor maybe 90% of use cases, you will only need to modify the mustache template files to create your own custom generated code.

Export android studio project as template