Open wolfdale opened 4 years ago
Hi @wolfdale this would be a realy nice feature. I am looking forward for something like this. Thank you, Sebastian
I am interested as well!
is there any update on this topic? A feature like this would be very helpful.
I am interested as well!
Would be awesome to have this. If someone points me to the code, I could have a look how to do it.
don't the tags offer this functionality?
tag your operations accordingly and add <useTags>true</useTags>
to your plugin configuration's configOptions(assuming maven pom)
@dwilda can you please give an example of yaml file, java file and maven configuration
@dwildapuoi fornire un esempio di file yaml, file Java e configurazione Maven
Hi, I attached example yaml and maven-plugin and next put screen of result
result:
You can mark your endpoints with different tags:
/animal/mammals:
get:
tags:
- Mammals
/animal/reptiles:
get:
tags:
- Reptiles
and add configOptions in your build.gradle
openApiGenerate {
configOptions = [
useTags: "true",
]
}
Is your feature request related to a problem? Please describe.
Problem : If the URL starts with
/animal/mammals
Java openapi-generator will generate a API interface asAnimalApi
. Suppose we have another URL which starts with/animal/reptiles
, the generated APIs interfaceAnimalApi
will have all the APIs ofmammals
&reptiles
together.For modular design, sometimes it is necessary to segregate the APIs for
mammals
&reptiles
into different classes(with same starting URL - /animal/). In this particular case, it would be helpful if we can generate two separate interface likeAnimalMammalApi
&AnimalReptileApi
.Right now are no provision for controlling how we generate APIs interfaces.
Describe the solution you'd like
Need to have more control over on how we generate APIs interface.
Describe alternatives you've considered
NA
Additional context
NA