Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

AsOf schema names

See original GitHub issue

What are the steps to reproduce this issue?

Generate client using spec:

openapi: '3.0.0'
info:
  version: 1.0.0
  title: Test
  license:
    name: MIT
servers:
  - url: http://petstore.swagger.io/v1
paths:
  /colors:
    get:
      summary: List colors
      operationId: listColors
      tags:
        - colors
      responses:
        '200':
          description: An array of colors
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Color'
components:
  schemas:
    ColorType:
      type: string
      enum:
        - red
        - green
        - blue
    Color:
      type: object
      required:
        - color
      properties:
        type:
          allOf:
            - $ref: '#/components/schemas/ColorType'

What happens?

The result is:

export type ColorType = 'red' | 'green' | 'blue';


export const ColorType = {
  red: 'red' as ColorType,
  green: 'green' as ColorType,
  blue: 'blue' as ColorType,
};

export type ColorType = ColorType

export const ColorType = {...ColorType};

export interface Color {
  type?: ColorType;
}

The second type-const pair uses the same name as the first pair, resulting in Cannot redeclare block-scoped variable 'ColorType'.ts (2451)

What were you expecting to happen?

Some other name of the second type. Maybe keep ColorTypeAllOf?

Any other comments?

I traced the issue to here: https://github.com/anymaniax/orval/blob/master/src/core/resolvers/value.ts#L22 And noticed that the name parameter to resolveValue is ColorTypeAllOf, but the returned name from resolveRef is ColorType.