Skip to content

Revisit server1/server2 and case1/case2 and value1/value2 naming in Servers, oneOf, allOf/anyOf #28

Open
@czechboy0

Description

@czechboy0

Revisit server1/server2 and case1/case2 and value1/value2 naming in Servers, oneOf, allOf/anyOf.

We don't like the names, we should derive better unique names, e.g. based on:

  • Swift type
  • JSON path
  • user-provided description
  • something else inherent

We just have to keep in mind that in many cases (e.g. inline schemas), we don't have a unique name to use, and might need to derive one - there we need to watch out for potential naming conflicts.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/usabilityUsability of generated code, ergonomics.status/needs-designNeeds further discussion and a concrete proposal.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions