Technologies Natives

Customize OpenAPI Generator output for your Android App

Getting started

What is OpenAPI (and Swagger)?

OpenAPI is a way to describe web services API. Basically, it allows to define API routes (with path, allowed parameters, HTTP verb...) and models (object models corresponding to API response or body and its components). All this information is contained in an OpenAPI specification written in YAML or JSON.

You may have heard about Swagger and its visible part Swagger UI. OpenAPI is simply the new name of Swagger after it has been transferred to the open-source community.

What is OpenAPI Generator?

Since the OpenAPI specification contains everything needed to interact with the API, we can generate the code required to interact with the API based on this file. And since REST API often expose a large data model with dozens of entities, it's very tenting to generate them. For exemple, the Twitter API used in this article is composed of more than 180 entities that you would have to write by hand.

Fortunately, OpenAPI Generator can generate everything from the model classes to an entire Gradle module for your data layer!

Install OpenAPI Generator

Open API Generator can be integrated using a Gradle plugin, but during development, I recommend using the CLI client which is more convenient during the configuration of the project.

Get the OpenAPI specification for your web service

This is the part where there is no magic. If the backend is developed by a separate team, they should already give you a corresponding OpenAPI or Swagger specification as part of the webservice documentation.

The goal of this article is not to cover how to write an OpenAPI specification, so let's take an existing one!

Basic generation

As an example, we can get a public API specification from Twitter.

In a new directory, download the specification file:

++code>$ wget https://api.twitter.com/2/openapi.json
++/code>

Then, let’s generate some code based on this:

++code>$ openapi-generator generate -g kotlin -i openapi.json++/code>

The command ++code>generate++/code> indicates that you want to generate something based on the ++code>-i++/code> ++code>openapi.json++/code> file. The ++code>-g++/code> option indicates the generator you want to use.

Dozens of languages and platforms are supported such as ++code>swift5++/code>, ++code>typescript++/code>, ++code>python++/code>... You can see all supported generators with ++code>$ openapi-generator list++/code>.

Run the command, and boom: An entire Kotlin SDK for Twitter has been generated!

1-generated-models-in-intellij

what’s available?

There is now a complete standalone Gradle module with:

  • Gradle build files

API documentation (Markdown) in ++code>docs

2-generated-documentation-in-markdown

++/code>

++code>++/code>

  • API models in ++code>src/.../models++/code>
  • Contains all model classes specified by the specification, and used by the endpoints. By default, Moshi JSON parser is used for serialization.
3-generated-model-in-kotlin

  •  
  • API methods in ++code>src/.../apis++/code>
  • Contains a method for every endpoint specified, using ++code>OkHttp++/code> by default as a client.
4-generated-method-in-kotlin
  • And since comments are generated from the specification file, it’s probably more commented than hand-written code!

Customization

Generate only some parts of the module

Generating the whole module is a good starting point to see what’s available, but it may be difficult to integrate into your current architecture. For instance, you may already have a configured OkHttp instance to use, and want to use Retrofit. At the end, we may be only interested in generating the model classes and the API classes.

Use the ++code>--global-property models --global-property apis++/code> options to generate only these classes.

As an example, wouldn’t it be nice to put these classes directly into your ++code>app++/code> module? Let’s add more options:

++code>-o app++/code> will target this directory for the generated code

++code>--model-package "com.myapp.mydatalayer.entities"++/code> Allows control in which package the model classes are generated

++code>--api-package "com.myapp.mydatalayer.api" ++/code>will do the same for the API classes.

Customize your models

At this point we may not want to use Moshi as a parser. Want to use the fancy ++code>kotlinx.serialization++/code>? Add this option:

++code>--additional-properties=serializationLibrary=kotlinx_serialization++/code>

++code>gson++/code> and ++code>jackson++/code> are also supported.

It is a good practice to identify at a glance if a model class is used in your data layer or your domain layer. Let’s add an ++code>Entity++/code> suffix to allow that!

++code>--model-name-suffix "Entity"++/code>

Now, all model classes end with this.

5-entity-suffix-in-model-file-names

Customize API interface files

Now, we may want to use our good old friend Retrofit for the API.

Let’s add this to ++code>--additional-properties=library=jvm-retrofit2,...++/code>

To use Kotlin coroutines for the Retrofit interface: ++code>--additional-properties=useCoroutines=true,...++/code>

Note that ++code>additional-properties++/code> should be concatenated using ++code>,++/code>our final option looks like: ++code>--additional-properties=library=useCoroutines=true,jvm-retrofit2,serializationLibrary=kotlinx_serialization++/code>

Use custom templates

If you tried to compile the module at the previous steps, you may have found that it, unfortunately, doesn’t compile 😭. As meta-programming is very powerful, it’s also a common pitfall you may encounter, so let’s try to fix this!

OpenAPI-generator works with templates written with the mustache template language. To access the templates used previously, use the ++code>author template++/code> command.

++code>$ openapi-generator author template -g kotlin -o template++/code>

You can then browse the template directory. Some interesting files:

  • ++code>data_class.mustache++/code>, ++code>data_class_opt_var.mustache++/code> and ++code>data_class_req_var.mustache++/code> are used to generate the models.
  • ++code>libraries/jvm-retrofit2/api.mustache++/code> is used to generate the Retrofit API interfaces that we configured previously.
  • ++code>licenseInfo.mustache++/code> is the header for the model classes.

The purpose of this is not to explain the mustache template language, but some fixes on the templates were necessary.

build.gradle integration

Finally, we want to be able to generate the file on demand without having to install the CLI client.

The OpenAPI Generator Gradle plugin make it possible!

After having setup the plugin,

Let’s convert the command line we’ve been methodically building to a set of option:

++pre>++code>openApiGenerate {
globalProperties = [
supportingFiles: "",
apis : "",
models : "",
]
inputSpec = "openapi.json"
generatorName = "kotlin"
outputDir = "$rootDir/app"
templateDir = "template"
modelPackage = "fr.haan.openapi_playground_app.data.entities"
apiPackage = "fr.haan.openapi_playground_app.data.api"
modelNameSuffix = "Entity"
additionalProperties = [
useCoroutines : "true",
library : "jvm-retrofit2",
serializationLibrary: "kotlinx_serialization",
sourceFolder : "src/main/java",
]
}
++/code>++/pre>

We can now generate using gradle CLI: ++code>$ ./gradlew openApiGenerate++/code>

That’s it! Our app is now ready to follow the backend REST API developments without having to manually write entities or interfaces!

Final thoughts

As you can see, a lot of power comes from the spec being perfectly written (with strong types, accurate documentation, etc...) I guess the best way to achieve this is to also generate the server side using the same specification.

Anyway, I hope you enjoyed reading this! You will find the complete step-by-step repository with all the example code of this article here.

Développeur Mobile ?

Rejoins nos équipes