Case that is UNclear in the spec: Discriminator with array

[Gallimathias]

I have the following case:

My Api call returns a Variant that contains a bool as discriminator. The two values are either an error object or an array of a value.

Example: (no valid code)

success: boolean
value:
  oneOf:
    {errorCode: number, message: string}
    arrayOf {description: string, data: {...} ...}

Descriminator:

discriminator:
  propertyName: success
  mapping:
   false: '#/components/shema/Error'
   true: ????? 

The problem is that in the discriminator mapping only the schema of the items contained in the array can be referenced because no seperate schema is made for arrays.

For the autogeneration, however, which pays attention to the discriminator, it is now necessary to recognise both fields separately or, from my point of view, responses and discriminator then contradict each other

Did i miss something and there is already a solution for that?

[LasneF]

according to https://github.com/OAI/OpenAPI-Specification/blob/main/schemas/v3.0/schema.yaml#L335 looks discriminator can only be a string , not a boolean

same here

OpenAPI-Specification/schemas/v3.1/meta/base.schema.json

Line 29 in 6458d30

"discriminator": {

so there is a kind of mapping conflict between boolean and string

[handrews]

@Gallimathias – @LasneF is correct. The property named in propertyName must have a string value. This is not directly specified (the schema is not normative), so I have filed #3475 to track that specific spec problem more clearly. I'm going to close this now that we're tracking the underlying issue, but please feel free to comment further if we missed something.