deps: update to @bpmn-io/element-templates-validator@2.0.1

[marstamm]

closes #70

[barmac]

I tried this out and it seems that the implementation sets the value like "feel: static":

Further edits add the equal sign in the front of expression =

[barmac]

Consider moving test templates to test/spec/fixtures so that they are accessible via npm start script.

[barmac]

Alternatively, we could force the template developers to set value to expression if feel is set to required.

[barmac]

Something like:

{
  "if" {
    "required": [ "feel" ]
    "properties": {
      "feel": {
        "const": "required"
      }
    }
  },
  "then": {
    "properties": {
      "value": {
        "type": "string",
        "pattern": "^="
      }
    }
  }
}

[marstamm]

IMO, we should not do magic to default values as well, it is confusing enough as it is. If you are using feel: required, the default value should be a feel expression. This fix is to prevent blowing up the editor when an unexpected value is provided.

I think we should add this check to the schema as well

[barmac]

Will you add this to the JSON schema then? It will make the test case invalid.

[marstamm]

Yes, I will add the JSON schema

[marstamm]

I removed the previous implementation since it is now enforced via the schema. It would have made more sense to do the type casting at the lower level code editor implementation anyway.