Use uiSchema to customize oneOf/anyOf with different types

[epicfaace]

Prerequisites

• I have read the documentation;
• In the case of a bug report, I understand that providing a SSCCE example is tremendously useful to the maintainers.

Description

I would like to use oneOf with different types. (another way of solving the problem in issue #282)

Steps to Reproduce

Use this schema:

{
  "type": "object",
  "properties": {
    "name": {
      "oneOf": [
        {
          "type": "string"
        },
        {
          "type": "number"
        }
      ]
    }
  }
}

Playground link

Expected behavior

Want to be able to select different types.

Actual behavior

I get this:

Version

1.2.0

[LucianBuzzo]

@epicfaace If you input a value you'll notice that it is coerced into a number or string depending on the option you selected. By default this module uses a "text" input to render number fields, which is why it looks like there is no change.
Normally you'd be able to use UISchema to change the widget used (for example to change it to a range or number input), however this doesn't currently work with anyOf/oneOf.

[loganvolkers]

Normally you'd be able to use UISchema to change the widget used (for example to change it to a range or number input), however this doesn't currently work with anyOf/oneOf.

That sounds like something worth fixing

[acronymhaterheidi]

I have encountered nearly the same issue in that I would like to use oneOf with an object and a basic type. I also want to use this oneOf inside an array. The oneOf works differently inside and outside of an array.

Here is the oneOf schema by itself:

{
  "oneOf": [
    {
      "type": "integer"
    },
    {
      "type": "object",
      "properties": {
        "elt1": {
          "type": "integer"
        },
        "elt2": {
          "type": "string"
        }
      },
      "required": [
        "elt1",
        "elt2"
      ]
    }
  ]
}

With a playground link.

This works fairly well although it is a little glitchy.

And the same schema within an array:

{
  "type": "object",
  "properties": {
    "myArray": {
      "type": "array",
      "items": {
        "oneOf": [
          {
            "type": "integer"
          },
          {
            "type": "object",
            "properties": {
              "elt1": {
                "type": "integer"
              },
              "elt2": {
                "type": "string"
              }
            },
            "required": [
              "elt1",
              "elt2"
            ]
          }
        ]
      }
    }
  }
}

With a playground link

This displays completely different behavior from the previous schema and does not allow input for the second option.

[LucianBuzzo]

@Rasstrelnikov Since you have reported a separate problem, I've opened a new issue to track it #1168

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please leave a comment if this is still an issue for you. Thank you.