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
for example <useTags>true</useTags> will produce several interfaces: DocumentApi, MaterialTypeApi, MaterialGroupApi...
The other solution is to remove /catalog/v1/api from the endpoints and use only the relevant end (for example /material-types/{id})
-> it will produce a MaterialTypesApi interface
then you have 2 options:
add the following to your contract.
servers:
- url: /catalog/v1/api
and correctly configure the configOptions requestMappingMode.
either add @RequestMapping("/catalog/v1/api") to your controllers
@jpfinne I mean, that it adds @tag annotation of Document type on a controller class and either additional tags on endpoints. So it makes additional tag for every endpoint so that I see that all endpoints belongs to Document Type tag which is wrong behaviour. Thank you for your impact!
Bug Report Checklist
Description
I identified several common tags for the API in the specification file
openapi-generator version
7.5.0
OpenAPI declaration file content or url
Generation Details
I use configuration in the mvn pom.xml
And I see result of
And it makes for every request additional tag of Document Type when only several requests belong to it
Steps to reproduce
execution of mvn clean package
Related issues/PRs
Didn't found any
Suggest a fix
I didn't find workaround for that
The text was updated successfully, but these errors were encountered: