Support more complex elements in settings

[Buckwich]

Problem you would like to solve

I would like to edit a more complex type in settings. For example I would like to have support for arrays (maybe visualized as tables), radio buttons, or conditional elements

Proposed solution

Add support for:

• radio buttons
• password fields
• section descriptions
• expandable table
• conditionals (inspired by [element templates] (https://docs.camunda.io/docs/components/modeler/desktop-modeler/element-templates/defining-templates/#defining-conditional-properties) (equals, oneOf, matchAll))
• validation

Alternatives considered

• Hardcoding custom components in modeler
• Passing custom components from plugins

Additional context

Tech enabler for https://github.com/camunda/product-hub/issues/2970

[jarekdanielak]

I'd like to see how we can extend the existing schema to enable this. Below is my proposal of a schema that should end up in rendering something similar to this mock.

Does it meet all requirements?

Settings form:

Source: https://github.com/camunda/product-hub/issues/2970#issuecomment-3035064660

Settings schema:

{
  "app.endpoints": {
    "type": "array",
    "label": "Manage Endpoints",
    "itemLabel": "Endpoint",
    "items": {
      "type": "object",
      "properties": {
        "app.endpoints.name": {
          "type": "text",
          "label": "Name",
          "default": ""
        },
        "app.endpoints.url": {
          "type": "text",
          "label": "URL",
          "default": "",
          "pattern": "^https?:\/\/"
        },
        "app.endpoints.authType": {
          "type": "radio",
          "label": "Authentication Type",
          "default": "none",
          "options": [
            { "value": "none", "label": "None" },
            { "value": "basic", "label": "Basic" }
          ]
        },
        "app.endpoints.tenantId": {
          "type": "text",
          "label": "Tenant ID",
          "default": "",
          "visibleIf": {
            "authType": "basic"
          }
        }
      }
    }
  }
}

[Buckwich]

Yes something like this could work. But we will probably also need something to disable fields (I'm currently trying to get around that). In order to support that (even if we don't use it) i was thinking to go more the directions of rules (enable,disable,show,hide) as https://jsonforms.io/docs/uischema/rules

One thing i like about jsonforms is also that they differentiate the data and ui schema. for example we may want to show array data in a table one time and as a list another time. or also layouting for the radio buttons (horizontal vs vertical)