Standalone UI: Available values for discriminated union of enumerations in request body

Q&A (please complete the following information)

• OS: [e.g. Windows 10]
• Browser: [chromium edge]
• Version: [116.0.1938.62]
• Method of installation: [NuGet with AspNetCore 6.0]
• Swagger-UI version: [4.5.15]
• Swagger/OpenAPI version: [OpenAPI 3.0.1]

Content & configuration

Swagger/OpenAPI definition:

openapi: 3.0.1
info:
  title: Sample
  version: '1.1'
paths:
  '/toggles/{name}':
    put:
      operationId: ChangeToggle
      parameters:
        - name: name
          in: path
          required: true
          schema:
            enum:
              - A
              - B
            type: string
      requestBody:
        content:
          application/json:
            schema:
              type: string
              oneOf:
                - $ref: '#/components/schemas/AValues'
                - $ref: '#/components/schemas/BValues'
              discriminator:
                propertyName: name
                mapping:
                  A: '#/components/schemas/AValues'
                  B: '#/components/schemas/BValues'
        required: true
      responses:
        '200':
          description: Success
components:
  schemas:
    AValues:
      enum:
        - A1
        - A2
      type: string
    BValues:
      enum:
        - B1
        - B2
      type: string

Screenshots

How can we help?

For the name parameter Swagger-UI shows handy dropdown and lists available values.
However for the requestBody parameter there is no equivalent UX. In addition, the only place were request body is related to oneOf element is in "Schema" tab which is not really user friendly.

I suggest to implement support for oneOf between enumerated schemas such that request body example value

1. Is presented as a dropdown with values currently valid for the current selection of the name parameter
2. There is similar comment, Available values

Reproduce the standalone UI with the supplied OpenAPI 3.0.1 definition and inspect the requestBody example controls alongside the Schema tab. Trace how the name parameter selection and oneOf enumerated schemas are rendered; done means the request body offers only the currently valid enum values and includes an Available values comment.