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
  • #2844
Closed
Open
Issue created May 08, 2019 by Administrator@rootContributor

[ASPNETCORE] multiple tags for a method generates multiple controllers

Created by: magnayn

Description

Multiple tags create multiple server endpoints

openapi-generator version

4.0.0-beta3

OpenAPI declaration file content or url

This is more a query (is there not a ML/community for this sort of thing?).

I've declared tags in the OpenAPI specification, to thematically collect API calls around various use-cases.

Thus API methods may have several tags. This is very useful in documentation generation.

But when aspnetcore generation occurs, you get a controller per tag - which doesn't seem right at all - not least of which the URL is identical in both.

There seems to be an assumption that a method has only one tag (maybe?) for the server end.

There doesn't seem to be a nice way to split up big APIs in OpenAPI that works nicely. Unless I'm missing something..

Assignee
Assign to
Time tracking