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
Copy file name to clipboardExpand all lines: docs/generators/java-camel.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,6 +88,7 @@ These options may be applied as additional-properties (cli) or configOptions (pl
88
88
|resourceFolder|resource folder for generated resources||src/main/resources|
89
89
|responseWrapper|wrap the responses in given type (Future, Callable, CompletableFuture,ListenableFuture, DeferredResult, RxObservable, RxSingle or fully qualified type)||null|
90
90
|returnSuccessCode|Generated server returns 2xx code||false|
91
+
|schemaImplements|Ability to supply interfaces per schema that should be implemented (serves similar purpose as vendor extension `x-implements`, but is fully decoupled from the api spec). Example: yaml `schemaImplements: {Pet: com.some.pack.WithId, Category: [com.some.pack.CategoryInterface], Dog: [com.some.pack.Canine, com.some.pack.OtherInterface]}` implements interfaces in schemas `Pet` (interface `com.some.pack.WithId`), `Category` (interface `com.some.pack.CategoryInterface`), `Dog`(interfaces `com.some.pack.Canine`, `com.some.pack.OtherInterface`)||empty map|
91
92
|scmConnection|SCM connection in generated pom.xml||scm:git:git@github.com:openapitools/openapi-generator.git|
92
93
|scmDeveloperConnection|SCM developer connection in generated pom.xml||scm:git:git@github.com:openapitools/openapi-generator.git|
93
94
|scmUrl|SCM URL in generated pom.xml||https://github.com/openapitools/openapi-generator|
@@ -119,6 +120,7 @@ These options may be applied as additional-properties (cli) or configOptions (pl
119
120
|useTags|use tags for creating interface and controller classnames||false|
120
121
|virtualService|Generates the virtual service. For more details refer - https://github.com/virtualansoftware/virtualan/wiki||false|
121
122
|withXml|whether to include support for application/xml content type and include XML annotations in the model (works with libraries that provide support for JSON and XML)||false|
123
+
|xImplementsSkip|Ability to choose interfaces that should NOT be implemented in the models despite their presence in vendor extension `x-implements`. Takes a list of fully qualified interface names. Example: yaml `xImplementsSkip: [com.some.pack.WithPhotoUrls]` skips implementing the interface `com.some.pack.WithPhotoUrls` in any schema||empty list|
Copy file name to clipboardExpand all lines: docs/generators/kotlin-spring.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,6 +43,8 @@ These options may be applied as additional-properties (cli) or configOptions (pl
43
43
|parcelizeModels|toggle "@Parcelize" for generated models||null|
44
44
|reactive|use coroutines for reactive behavior||false|
45
45
|requestMappingMode|Where to generate the class level @RequestMapping annotation.|<dl><dt>**api_interface**</dt><dd>Generate the @RequestMapping annotation on the generated Api Interface.</dd><dt>**controller**</dt><dd>Generate the @RequestMapping annotation on the generated Api Controller Implementation.</dd><dt>**none**</dt><dd>Do not add a class level @RequestMapping annotation.</dd></dl>|controller|
46
+
|schemaImplements|A map of single interface or a list of interfaces per schema name that should be implemented (serves similar purpose as `x-kotlin-implements`, but is fully decoupled from the api spec). Example: yaml `schemaImplements: {Pet: com.some.pack.WithId, Category: [com.some.pack.CategoryInterface], Dog: [com.some.pack.Canine, com.some.pack.OtherInterface]}` implements interfaces in schemas `Pet` (interface `com.some.pack.WithId`), `Category` (interface `com.some.pack.CategoryInterface`), `Dog`(interfaces `com.some.pack.Canine`, `com.some.pack.OtherInterface`)||empty map|
47
+
|schemaImplementsFields|A map of single field or a list of fields per schema name that should be prepended with `override` (serves similar purpose as `x-kotlin-implements-fields`, but is fully decoupled from the api spec). Example: yaml `schemaImplementsFields: {Pet: id, Category: [name, id], Dog: [bark, breed]}` marks fields to be prepended with `override` in schemas `Pet` (field `id`), `Category` (fields `name`, `id`) and `Dog` (fields `bark`, `breed`)||empty map|
46
48
|serializableModel|boolean - toggle "implements Serializable" for generated models||null|
47
49
|serverPort|configuration the port in which the sever is to run on||8080|
48
50
|serviceImplementation|generate stub service implementations that extends service interfaces. If this is set to true service interfaces will also be generated||false|
@@ -59,6 +61,8 @@ These options may be applied as additional-properties (cli) or configOptions (pl
59
61
|useSpringBoot3|Generate code and provide dependencies for use with Spring Boot ≥ 3 (use jakarta instead of javax in imports). Enabling this option will also enable `useJakartaEe`.||false|
60
62
|useSwaggerUI|Open the OpenApi specification in swagger-ui. Will also import and configure needed dependencies||true|
61
63
|useTags|Whether to use tags for creating interface and controller class names||false|
64
+
|xKotlinImplementsFieldsSkip|A list of fields per schema name that should NOT be created with `override` keyword despite their presence in vendor extension `x-kotlin-implements-fields` for the schema. Example: yaml `xKotlinImplementsFieldsSkip: Pet: [photoUrls]` skips `override` for `photoUrls` in schema `Pet`||empty map|
65
+
|xKotlinImplementsSkip|A list of fully qualified interfaces that should NOT be implemented despite their presence in vendor extension `x-kotlin-implements`. Example: yaml `xKotlinImplementsSkip: [com.some.pack.WithPhotoUrls]` skips implementing the interface in any schema||empty list|
Copy file name to clipboardExpand all lines: docs/generators/spring.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,6 +81,7 @@ These options may be applied as additional-properties (cli) or configOptions (pl
81
81
|resourceFolder|resource folder for generated resources||src/main/resources|
82
82
|responseWrapper|wrap the responses in given type (Future, Callable, CompletableFuture,ListenableFuture, DeferredResult, RxObservable, RxSingle or fully qualified type)||null|
83
83
|returnSuccessCode|Generated server returns 2xx code||false|
84
+
|schemaImplements|Ability to supply interfaces per schema that should be implemented (serves similar purpose as vendor extension `x-implements`, but is fully decoupled from the api spec). Example: yaml `schemaImplements: {Pet: com.some.pack.WithId, Category: [com.some.pack.CategoryInterface], Dog: [com.some.pack.Canine, com.some.pack.OtherInterface]}` implements interfaces in schemas `Pet` (interface `com.some.pack.WithId`), `Category` (interface `com.some.pack.CategoryInterface`), `Dog`(interfaces `com.some.pack.Canine`, `com.some.pack.OtherInterface`)||empty map|
84
85
|scmConnection|SCM connection in generated pom.xml||scm:git:git@github.com:openapitools/openapi-generator.git|
85
86
|scmDeveloperConnection|SCM developer connection in generated pom.xml||scm:git:git@github.com:openapitools/openapi-generator.git|
86
87
|scmUrl|SCM URL in generated pom.xml||https://github.com/openapitools/openapi-generator|
@@ -112,6 +113,7 @@ These options may be applied as additional-properties (cli) or configOptions (pl
112
113
|useTags|use tags for creating interface and controller classnames||false|
113
114
|virtualService|Generates the virtual service. For more details refer - https://github.com/virtualansoftware/virtualan/wiki||false|
114
115
|withXml|whether to include support for application/xml content type and include XML annotations in the model (works with libraries that provide support for JSON and XML)||false|
116
+
|xImplementsSkip|Ability to choose interfaces that should NOT be implemented in the models despite their presence in vendor extension `x-implements`. Takes a list of fully qualified interface names. Example: yaml `xImplementsSkip: [com.some.pack.WithPhotoUrls]` skips implementing the interface `com.some.pack.WithPhotoUrls` in any schema||empty list|
0 commit comments