Skip to content

map inline names to nicer names #189

@hauner

Description

@hauner
  /bookings/{bookingId}/payment:
    post:
      responses:
        '200':

generates the response object as BookingsBookingIdPaymentPostResponse200.

Would it be useful to have the possibility to map that identifier to a nicer name?

mapping could use

  • json path to nice java name
  • generated java name to nice java name

the processor would have to warn if the inline name did not exists.

benefit:

it would not be necessary to define responses etc. as named schema to get a proper java class name

drawback:

harder to maintain?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions