Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • O openapi-generator
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3,476
    • Issues 3,476
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 402
    • Merge requests 402
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenAPI Tools
  • openapi-generator
  • Issues
  • #11843
Closed
Open
Issue created Mar 10, 2022 by Administrator@rootContributor

[REQ] A way to access a non-duplicated set of all APIs with multiple tags

Created by: hallami

Is your feature request related to a problem? Please describe.

Right now, all APIs are bundled by their tags. APIs with multiple tags end up in multiple bundles, meaning duplicates of those APIs. I'd like a way to access a set (no duplicates) of the APIs.

Describe the solution you'd like

I'd like for there to either be a data section added under/around the apiInfo section that has the APIs not grouped by tags, or for there to be a flag that makes the generator ignore the tags attached to apis.

Describe alternatives you've considered

Going through and stripping out the tags

This means that I'm changing the specification, even if it shouldn't alter any performance.

Manually revising the output

This isn't practical and means that we can't run with the output straight out of the box.

Including tags in the naming schema

This skirts past the name collision issue, but then you still have totally duplicated code with a more confusing name scheme.

Additional context

I've found 3 previous issues that have ran into this same core problem that weren't submitted as requests: https://github.com/OpenAPITools/openapi-generator/issues/312 https://github.com/OpenAPITools/openapi-generator/issues/2844 https://github.com/OpenAPITools/openapi-generator/issues/8121

Assignee
Assign to
Time tracking