Using itemProperties directive does not allow configuration of required item fields

[Persi]

Currently using the following config:

myProp: [] # @schema description: cool prop ; uniqueItems:true ; item:object ; itemProperties:{"prop1": {"type": "string"}, "prop2": {"type": "string"}}

results in the following schema:

    "myProp": {
      "description": "cool prop",
      "items": {
        "properties": {
          "prop1": {
            "type": "string"
          },
          "prop2": {
            "type": "string"
          }
        },
        "type": "object"
      },
      "type": "array",
      "uniqueItems": true
    },

This schema does not define required fields of the item elements.
It would be helpful if there would be a directive to define the required item fields which would result in a schema like that:

    "myProp": {
      "description": "cool prop",
      "items": {
        "properties": {
          "prop1": {
            "type": "string"
          },
          "prop2": {
            "type": "string"
          },
        },
        "type": "object",
        "required": ["prop1", "prop2"]
      },
      "type": "array",
      "uniqueItems": true
    },

[losisin]

for now, required works as boolean and key is declared in yaml. I'll think about it if that behaviour should be changed
https://github.com/losisin/helm-values-schema-json/tree/main/docs#required