OpenAPITools / OpenAPITools/openapi-generator
[REQ] A way to access a non-duplicated set of all APIs with multiple tags
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No implementation files or tests are named. Start by reviewing the related issues 312, 2844, and 8121, then trace how APIs are currently bundled by tags in OpenAPI Generator. Done means providing a supported way to access APIs once, without changing the source specification or manually revising generated output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, openapi
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100