Wrong OAS30 object type definition which faultily inherits from string

[Jules Sam. Randolph]

oas-raml-coverter version 1.1.35

The OAS parser used by ReDoc project complains about a forbidden definition:

Error: Incompatible types in allOf at "#/components/schemas/BarFromFoo"

BarFromFoo should not be of "type": "string"

Full reproduction

Raml definition

types:
  Foo:
    type: object
  BarFromFoo:
    type: Foo
    properties:
      foo: string

Expected output

{
  "components": {
    "schemas": {
      "Foo": {
        "type": "object"
      },
      "BarFromFoo": {
        "allOf": [
          {
            "$ref": "#/components/schemas/Foo"
          },
          {
            "properties": {
              "foo": {
                "type": "string"
              }
            },
            "type": "object"
          }
        ]
      }
    }
  }
}

Observed output

{
  "components": {
    "schemas": {
      "Foo": {
        "type": "object"
      },
      "BarFromFoo": {
        "allOf": [
          {
            "$ref": "#/components/schemas/Foo"
          },
          {
            "properties": {
              "foo": {
                "type": "string"
              }
            },
            "type": "object"
          }
        ],
        "type": "string"
      }
    }
  }
}

[Jules Sam. Randolph]

Full reproduction available here: https://github.com/jsamr/oas-raml-converter-wrongly-inherits-string

[yingqiaoshop]

According to the OpenAPI 3.0 specification, for allOf, anyOf, oneOf keywords, there is no need to have the definition on type. So, maybe, one solution is just not to generate "type:" when those keywords are generated.