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
Is your feature request related to a problem? Please describe.
I have two or more microservices that each have their own OpenAPI specification file. I aimed to join them together to build the complete API specification.
Each service has its own tags and x-tagGroups configuration. I could not find a way to retain & merge the existing x-tagGroups from all specifications together. They are either regenerated and all tags are grouped by specification name, or just ignored, depending on the --without-x-tag-groups option.
I would like the final output to contain a unique list of all tag groups of every specification.
If the same tag group exists within different specifications, I would like to see their tags merged together.
I think that duplicate tags should not cause a "conflict" in this new scenario.
Maybe the current behaviour can be kept by introducing this new behaviour as a new option, or vice versa?
Describe alternatives you've considered
There is the option --without-x-tag-groups:
If not set, it will merge all tags and group them into a x-tagGroup which is based on the specification name.
If set, it will skip the above automated creation of x-tagGroups. Unfortunately, the x-tagGroups property is then not created in the joined file at all
Unfortunately this means that the existing x-tagGroups information is not used. Furthermore, you always see a warning:
warning: x-tagGroups at src/services/common/openapi.yaml will be skipped
Additional context
Example (merge A + B together, with a duplicate x-tagGroup Invoicing:
Is your feature request related to a problem? Please describe.
I have two or more microservices that each have their own OpenAPI specification file. I aimed to
join
them together to build the complete API specification.Each service has its own
tags
andx-tagGroups
configuration. I could not find a way to retain & merge the existingx-tagGroups
from all specifications together. They are either regenerated and all tags are grouped by specification name, or just ignored, depending on the--without-x-tag-groups
option.x-tagGroups
injoin
command #1314Describe the solution you'd like
I would like the final output to contain a unique list of all tag groups of every specification.
If the same tag group exists within different specifications, I would like to see their tags merged together.
I think that duplicate tags should not cause a "conflict" in this new scenario.
Maybe the current behaviour can be kept by introducing this new behaviour as a new option, or vice versa?
Describe alternatives you've considered
There is the option
--without-x-tag-groups
:x-tagGroup
which is based on the specification name.x-tagGroups
. Unfortunately, thex-tagGroups
property is then not created in the joined file at allUnfortunately this means that the existing
x-tagGroups
information is not used. Furthermore, you always see a warning:Additional context
Example (merge A + B together, with a duplicate x-tagGroup
Invoicing
:Specification A:
Specification B:
Intended result:
The text was updated successfully, but these errors were encountered: