If tosca functions are inputted into operation inputs the generated tosca template has them generated incorrectly. This happened for strings in lists, maps, objects, etc

Sample values pasted in:

On the operation inputs from vfc definition
input name: test
type: lsit
schema: string
subproperty: list of strings
values:

• {"get_property":["relatedParty_0","name"]}
• {"get_attribute":["relatedParty_0","name"]}
• {"get_input":["relatedParty_0","name"]}

   

//TEMPLATE FORMATTING
interfaces:
    Standard:
        type: tosca.interfaces.node.lifecycle.Standard
        delete:
            implementation: uri
            inputs:
                test:
                - '{"get_property":["relatedParty_0","name"]}'
                - '{"get_attribute":["relatedParty_0","name"]}'
                - '{"get_input":["relatedParty_0","name"]}'