OpenAPITools / OpenAPITools/openapi-generator
[REQ] Enable multi-spec generation in Gradle Plugin
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
In our codebase, we're using the domain gateway pattern. As a result, the service has 1 API spec that should serve as a service and multiple API specs that should serve as a client. The current implementation of the plugin does not allow to generate multiple specs easily, and therefore we came up with the following solution to our services:
- We defined a new class that represents a single-class generation
data class ApiSpec(
val name: String,
val taskName: String,
val directoryPath: String,
val outputDir: String,
val specFileName: String,
val generatorType: String,
val packageName: String,
val modelPackageName: String,
val config: Map<String, String>,
val templateDir: String? = null
)
- We create a list of the above classes where each of them represents the spec we need:
val supportedApis = listOf(
ApiSpec(
name = "Gateway API",
taskName = "generateGatewayApi",
directoryPath = apiDirectoryPath,
templateDir = "$apiDirectoryPath/templates/kotlin-spring",
outputDir = "$openApiGenerateOutputDir/domain-gateway",
specFileName = "gateway-api.yaml",
generatorType = "kotlin-spring",
packageName = "com.yonatankarp.gateway.openapi.v1",
modelPackageName = "com.yonatankarp.gateway.openapi.v1.models",
config = mapOf(
"dateLibrary" to "java8",
"interfaceOnly" to "true",
"implicitHeaders" to "true",
"hideGenerationTimestamp" to "true",
"useTags" to "true",
"documentationProvider" to "none",
"useSpringBoot3" to "true",
)
),
ApiSpec(
name = "Hello API",
taskName = "generateHelloApi",
directoryPath = apiDirectoryPath,
outputDir = "$openApiGenerateOutputDir/domain-gateway",
specFileName = "hello-api.yaml",
generatorType = "kotlin",
packageName = "com.yonatankarp.hello.openapi.v1_current",
modelPackageName = "com.yonatankarp.hello.openapi.v1_current.models",
config = mapOf(
"dateLibrary" to "java8",
"interfaceOnly" to "true",
"implicitHeaders" to "true",
"hideGenerationTimestamp" to "true",
"useTags" to "true",
"documentationProvider" to "none",
"serializationLibrary" to "jackson",
"useCoroutines" to "true",
"library" to "jvm-retrofit2"
)
),
ApiSpec(
name = "Goodbye API",
taskName = "generateGoodbyeApi",
directoryPath = apiDirectoryPath,
outputDir = "$openApiGenerateOutputDir/domain-gateway",
specFileName = "goodbye-api.yaml",
generatorType = "kotlin",
packageName = "com.yonatankarp.goodbye.openapi.v1_current",
modelPackageName = "com.yonatankarp.goodbye.openapi.v1_current.models",
config = mapOf(
"dateLibrary" to "java8",
"interfaceOnly" to "true",
"implicitHeaders" to "true",
"hideGenerationTimestamp" to "true",
"useTags" to "true",
"documentationProvider" to "none",
"serializationLibrary" to "jackson",
"useCoroutines" to "true",
"library" to "jvm-retrofit2"
)
)
)
- For each of the above classes we create a new task that would generate the spec
supportedApis.forEach { api ->
tasks.create(api.taskName, GenerateOpenApiTask::class) {
group = "openapi tools"
description = "Generate the code for ${api.name}"
generatorName.set(api.generatorType)
inputSpec.set("${api.directoryPath}/${api.specFileName}")
outputDir.set(api.outputDir)
apiPackage.set(api.packageName)
modelPackage.set(api.modelPackageName)
configOptions.set(api.config)
api.templateDir?.let { this.templateDir.set(it) }
}
}
- Add the new tasks as dependencies to the same tasks the current implementation is using
tasks {
clean {
dependsOn("cleanGeneratedCodeTask")
supportedApis.forEach { finalizedBy(it.taskName) }
}
compileKotlin {
supportedApis.forEach { dependsOn(it.taskName) }
}
}
The complete solution example can be seen in this link.
Notes
- While our solution currently doesn't support global configuration, that would be useful to add while updating the plugin.
- The above requirements are breaking changes, and therefore might be considered as part of release
8.x.x
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the Gradle plugin implementation and its GenerateOpenApiTask configuration; compare the current single-spec setup with the linked domain-gateway example. Done means multiple API specs can define separate generation tasks, shared or global configuration is addressed, and the existing task dependencies continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100