[BUG] output transformers strips out fields with anyOf schema

[celleb]

Describe the bug
Properties with anyOf schema are striped out from output transformers.

Given the following schemas:
user/model.yml

anyOf:
  - $ref: ./driver/model.yml
  - $ref: ./passenger/model.yml
discriminator:
  propertyName: type

type: object
properties:
  token:
    type: string
    readOnly: true
    example: eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJ5Y3BCVzRKSU0zYWVE...
  user:
    $ref: user/model.yml
required:
  - user
  - token

Produces

export default {
  // authorize
  authorize: {
    token: String
  }
}

To Reproduce
Steps to reproduce the behavior:

1. Generate the backend from the swagger file
2. Inspect the generated output transformer

Expected behavior
The transformer has the correct fields and types or at least allows any field to pass.

Node & NPM version
Node: 12.18.2
NPM: 6.14.8

Operating system:

• OS: MacOS
• Version: 11.2.2

Additional context
Using OAS3

[Acrontum-Carmichael]

This feature from OA was never written in, PR welcomed :)

[Acrontum-Carmichael]

@celleb do you have any ideas for how we could accommodate the anyOf feature?

[celleb]

Is anyone working on this, maybe someone is thinking of a new type generator? Otherwise, I might jump on it.

[p-mcgowan]

Sorry for the late reply - we're all pretty slammed right now.

We've been talking about new type generators but nothing significant, so if you want to take a whack at it then go for it.

I haven't run into the issue myself, but I don't recall using anyOf lately so that's probably why. Would love to have proper oa3 support, and fixing typings would be an awesome start