Does OpenRPC supports something like "discriminator" for oneOf and anyOf?

[svetlyak40wt]

OpenAPI supports it and this feature is useful when writing code-generated API wrappers.

Here is how it looks like in the OpenAPI spec:

components:
  responses:
    sampleObjectResponse:
      content:
        application/json:
          schema:
            oneOf:
              - $ref: '#/components/schemas/Object1'
              - $ref: '#/components/schemas/Object2'
              - $ref: 'sysObject.json#/sysObject'
            discriminator:
              propertyName: objectType
              mapping:
                obj1: '#/components/schemas/Object1'
                obj2: '#/components/schemas/Object2'
                system: 'sysObject.json#/sysObject'

Example was taken from here.

[github-actions]

Welcome to OpenRPC! Thank you for taking the time to create an issue. Please review the guidelines

[etodanik]

This is similar to an earlier request:
#357

Would be great to hear which path maintainers prefer so someone could cook up a PR

[jeremyfiel]

JSON Schema draft-07 provides the if, then construct which is equivalent to discriminator without all the issues the discriminator keyword caused for OAS users

You can write a discriminator like so:

schema:
  properties:
    address: {}
    type:
      enum:
      - personal
      - business
  allOf:
  - if:
      properties:
        const: personal
    then:
      ...do-something...
    if:
      properties:
        const: business
    then:
      ...do-something-else...