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
  • #4399
Closed
Open
Issue created Nov 06, 2019 by Administrator@rootContributor

[REQ] Name inline object types based on context instead of `InlineResponseDefault*`

Created by: vbence

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

I am using either the jaxrs-cxf-client or the java generators. When, an OpenApi specification has inline definition for a request / response type a Java class name is generated based on an ordinal number. Example:

    public InlineResponseDefault22 doSomethingAwesome(InlineObject21 body);

Describe the solution you'd like

I'd like inline objects to be named based on context (the operationId or endpoint name) prefixed with their function like DoSomethingAwesomeRequest instead of InlineObject21 and DoSomethingAwesomeResponseOK instead of InlineObject21.

Describe alternatives you've considered

Anything predictable would be fine, because the current method breaks any references if the API gets some additions (even endpoints added - a non-breaking change - can move ordinal numbers around).

Additional context

Generally I want the code generation repeated any time (to follow upstream API changes). If existing references to InlineObject21 break, updating will be an hurdle.

Assignee
Assign to
Time tracking