fix(getters): handle OpenAPI 3.1 nullability

[geirsagberg]

Status

READY

Description

In OpenAPI 3.1, the nullable keyword has been removed, and nullability is handled by oneOf, anyOf or type arrays: https://www.openapis.org/blog/2021/02/16/migrating-from-openapi-3-0-to-3-1-0

Currently, Orval does not support this, with nullable types ending up as unknown (for type arrays) or e.g. string | unknown (for oneOf/anyOf).

This PR adds support both for oneOf, anyOf and type arrays:

components:
  schemas:
    NullableObject:
      type: object
      properties:
        name:
          type:
            - 'string'
            - 'null'
        age:
          anyOf:
            - type: 'integer'
            - type: 'null'
        address:
          oneOf:
            - type: 'string'
            - type: 'null'

Resulting in:

export interface NullableObject {
  name?: NullableObjectName
  age?: NullableObjectAge
  address?: NullableObjectAddress
}

export type NullableObjectAddress = string | null
export type NullableObjectAge = number | null
export type NullableObjectName = string | null

Also fixes #551 by interpreting type arrays as anyOf (as suggested by https://stackoverflow.com/a/48114924/500976)

Todos

• Tests

[vercel]

Someone is attempting to deploy a commit to a Personal Account owned by @anymaniax on Vercel.

@anymaniax first needs to authorize it.

[anymaniax]

Seems good thanks @geirsagberg

[geirsagberg]

Thanks for merging :D any ETA for next release?

[anymaniax]

it's release

[arthurfiorette]

Hey @anymaniax does support for union types with mock: true is being tested? I cannot get it to work :/

It generates correct typings, but the mock is being generated with a simple {} object.