Skip to content

JSONSchema case is not supported #180

@Geksanit

Description

@Geksanit

schema.yaml

...
components:
  schemas:
    BaseSchema:
      type: object
      properties:
        type:
          type: string
          enum: 
          - FOO
          - BAR
          - BAZ
      required:
      - type

    FooSchema:
      allOf:
      - $ref: '#/components/schemas/BaseSchema'
      - type: object
        properties:
          type:
            type: string
            enum:
            - FOO

It is correct JSONSchema
FooSchema equal type:
type FooSchema = { type: 'FOO' | 'BAR' | 'BAZ' } & { type: 'FOO' | undefined} -> { type: 'FOO' }
generated code:

export type BaseSchema = { type: 'FOO' | 'BAR' | 'BAZ' };
export type FooSchema = BaseSchema & { type: Option<'FOO'> };

Nothing can match type FooSchema. I understand that this is the result of a combination of optionFromNullable and intersection. It turns out that we do not fully support the JSONSchema. We could throw away the mistake of not supporting this case.
Let's discuss this and think about a solution.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions