Support 'oneOf' enum titles in array element headers

[low-on-mana]

Describe the bug
I am trying to add label to enum fields as described in this commit 432af77. Its resulting in weird recursive form.

To Reproduce
Jsonschema:

        "loadBalancer": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "type",
              "threshold",
              "duration",
              "severity"
            ],
            "properties": {
              // 3 other elements as in screenshot
              "severity": {
                "type": "string",
                "oneOf": [
                  {"const": "foo", "title": "Foo"},
                  {"const": "bar", "title": "Bar"}
                ],
                "default": "foo"
              }
            }
          }
        },

UISchema:

            {
              "type": "Control",
              "scope": "#/properties/deployment/properties/alerts/properties/loadBalancer",
              "label": "LoadBalancer alerts",
              "options": {
                "detail": {
                  "type": "VerticalLayout",
                  "elements": [
                    // 3 other elements as in screenshot
                    {
                      "type": "Control",
                      "scope": "#/properties/severity"
                    }
                  ]
                }
              }

Expected behavior
Expected to show usual dropdown with different title and value

Screenshots
Foo, Bar instead of coming as drop down are coming as category fields. And in these categories, my whole form is again inside.

Browser (please complete the following information):

• Browser [Firefox]
• Version [79.0]

Used Setup (please complete the following information):

• Framework: [react]
• RendererSet: [material]

Additional context
The said enum field is a field contained in array of objects, thats why I am using options->detail.

[sdirix]

The commit is not yet part of a "stable" release. Does it work for you when using @jsonforms/core@next, @jsonforms/react@next and @jsonforms/material-renderers@next? Instead of next you could also specify 2.4.1-alpha.3.

[low-on-mana]

Thanks that worked, I just checked the date of commit and didn't check release.

One small problem is that header of array item is showing the enum value instead of title.
In above screenshot latency is value of the type field, but its title is Latency (in ms)

Its not a major issue for my project. Close this ticket if needed, and appreciate the help.

[sdirix]

That's a good point. At the moment the logic for the header is not so smart and it just takes the first actual value it finds (except when configured differently via options.childLabelProp). We would need to add a check for this special case to check whether that prop is this special-oneOf enum and then map to the title.