Discriminator: Is mapping multiple property values to the same schema valid?

[Aweptimum]

I have a use-case where I have two objects, Comparison and Composite, that both share an operator property, but Composite has a collection of both itself and Comparisons. To discriminate, I figured I would use the operator property. Both Comparison and Composite have their own set of possible operators. I created a discriminator like this:

Any: {}
Condition:
      type: object
      properties:
        operator:
          type: string
      discriminator:
        propertyName: operator
        mapping:
          eq: "#/components/schemas/Comparison"
          neq: "#/components/schemas/Comparison"
          gte: "#/components/schemas/Comparison"
          lte: "#/components/schemas/Comparison"
          gt: "#/components/schemas/Comparison"
          lt: "#/components/schemas/Comparison"
          in: "#/components/schemas/Comparison"
          notIn: "#/components/schemas/Comparison"
          or: "#/components/schemas/Composite"
          and: "#/components/schemas/Composite"
      anyOf:
      - "$ref": "#/components/schemas/Comparison"
      - "$ref": "#/components/schemas/Composite"
    Comparison:
      description: Check a property meets some condition
      properties:
        property:
          type: string
        argument:
          "$ref": "#/components/schemas/Any"
        operator:
            "$ref": "#/components/schemas/ComparisonOperators"
      type: object
    Composite:
      description: Multiple Conditions
      properties:
        operator:
          "$ref": "#/components/schemas/CompositeOperators"
        conditions:
          type: array
          items:
            "$ref": "#/components/schemas/Condition"
      type: object
    ComparisonOperators:
      type: string
      enum:
      - eq
      - neq
      - lte
      - lt
      - gte
      - gt
      - in
      - notIn
    CompositeOperators:
      type: string
      enum:
      - andX
      - orX

And put it in swagger editor. It didn't complain, but I can't find a similar example. Was wondering if the mapping was meant to contain only unique One-To-One entries or if a Many-To-One like this is allowed.

[Aweptimum]

Ron Ratovsky answered in slack:

yes, it is perfectly valid.

[benazir-sba]

what about the ValueByDiscriminator function that is generated afterwards? Does it contain all the property values in its switch-case?

for me it does not. i have two different property values that should be mapped to the same schema. but the ValueByDiscriminator only includes one of the property values instead of both. and regeneration causes this property value to switch from one to the other but it never includes both

[Aweptimum]

If you're talking about the code generated by Swagger, the generator and the OpenAPI specification are two different things. The tooling around the OpenAPI specification may not conform to it 100%.