Orval Generating a Specific File for Union Types

[tarcisioandrade]

When we have a union types the orval creates a file and a specific type for it, instead of putting it inline.

Example:

AddressDto in Backend

AddressDto generated by orval

An AddressDtoStreat file was created instead of placed inline string | null.

Is there any setting that changes this behavior?

Version
"orval": "7.4.0"

[AllieJonsson]

How does the OpenAPI specification look like? Is there a lot of oneOf in the spec?

type: object
oneOf:
  - string
  - null

since this is not something that happens when the specification is something like

type: string
nullable: true

[tarcisioandrade]

How does the OpenAPI specification look like? Is there a lot of oneOf in the spec?

type: object
oneOf:

• string
• null
  since this is not something that happens when the specification is something like

type: string
nullable: true

Yes, my OpenAPI generates using oneOf.

So to solve this, I just have to prevent him from using oneOf, correct?

[AllieJonsson]

Yes, currently that is the only solution. If you cant change the actual spec, you could do some fiddeling in the input.transformer config setting to turn your

{
  "oneOf": [
    {
      "type": "null"
    },
    {
      "type": xxx
    }
  ]
}

Into

{
  "type": xxx,
  "nullable": true
}