binding allows invalid values

[nikku]

Describe the Bug

The schema validation for binding is insufficient, allowing to set properties not actually relevant to the existing binding type.

Steps to Reproduce

Validate the following template:

{
  "$schema": "https://unpkg.com/browse/@camunda/zeebe-element-templates-json-schema/resources/schema.json",
  "name": "Connector Name",
  "id": "connector-id",
  "appliesTo": ["bpmn:Task"],
  "properties": [
    {
      "type": "String",
      "binding": {
          "type": "zeebe:input",
          "name": "variableName",
          "key": "ONLY_RELEVANT_FOR_HEADERS"
      },
      "value": "=default expression"
    }
  ]
}

See that binding.key is an allowed property, despite only allowed if binding.type === 'zeebe:taskHeader'.

Expected Behavior

We validate known properties of binding, and ensure they are used correctly.

Environment

• Host (Browser/Node version), if applicable: Any
• OS: Any
• Library version: v0.12.0

[pinussilvestrus]

For transparency, in our draft forms JSON schema, we tried out a more modular approach of defining rules, e.g., also for allowed properties of sub schemas. One way to comprehend the fairly high complexity of these if-then-rules. Maybe this helps as an inspiration 👍

[nikku]

Would your approach directly contribute to better validation?

[pinussilvestrus]

This approach validates invalid properties for form field types, such as "if NOT this type, then this property is not allowed". IDEs with JSON schema support as VS Code then create such error messages.

[nikku]

Thanks for the update. So this would indeed fix #110.