[Go] Heterogeneous array with oneOf

[langston-barrett]

Description

Structs are not properly generated to handle arrays with item schema using oneOf. For instance, for the swagger.yml in the next section, an empty struct is generated:

type Bar struct {
}

This is what should be generated:

type Bar struct {
	Obj1 []string `xml:"Obj1"`
	Obj2 []bool   `xml:"Obj2"`
}

See the following Go playground: https://play.golang.org/p/rdNNL6nUUl1

openapi-generator version

Docker container version

OpenAPI declaration file content or url

---
openapi: 3.0.0
info:
  title: oneof
  version: 0.1.0

paths:
  "/foo":
    get:
      summary: foo
      responses:
        '200':
          description: OK
          content:
            application/xml:
              schema:
                "$ref": "#/components/schemas/Bar"

components:
  schemas:
    Bar:
      type: array
      items:
        oneOf:
        - $ref: '#/components/schemas/Obj1'
        - $ref: '#/components/schemas/Obj2'

    Obj1:
      type: string

    Obj2:
      type: bool

Command line used for generation

sudo docker run --rm -v ${PWD}:/local \
     openapitools/openapi-generator-cli generate \
     -i /local/swagger.yml \
     -g go \
     -o /local/generated/ \       
     -D withXml=true | grep -v INFO

Steps to reproduce

Related issues/PRs

#15

Suggest a fix/enhancement

The Go codegen should support arrays with oneOf schemata by integrating both/all types as list properties of the generated struct as in the above example.

[grokify]

oneOf is not yet supported in the core project. OAS3 features are being supported on a one by one basis right now.

A couple questions:

• Are you working on a public or private API? If it's public, can you share the spec?
• Is this model for a request, response, or both?

I'm tracking a number of specs here:

https://github.com/grokify/api-specs

So far, only one uses oneOf but it's a 2.0 spec, so not official.

https://github.com/grokify/api-specs/blob/master/salesforce/iot/v43.0.0/salesforce-iot-api-v43.0.0_swagger-v2.0.yaml#L3114-L3125

[langston-barrett]

Unfortunately, the API and spec are private. Both.

[grokify]

I see this is for a response in your example. Do you also use oneOf for request schemas?

[langston-barrett]

Yes, sorry I meant "both" to answer your second question.

[grokify]

Thanks for the clarification.

I've added a oneOf example schema to our example specs so we will be ready for testing when we have it.

#511