Feature Request - Command add - Support for JSON object with dynamic values

[ifranlaloe]

The command add does not support adding a JSON object with Dynamic values. I think that this could improve the readability, complexity and number of lines of a JLIO script by being able to combine multiple add commands.

[
  {
    "path": "$.TransfResult",
    "description": "Values",
    "value": {
      "orderId": "Static String",
      "orderDetails": "${$.request.orders[*].items[*].descriptions[*].details}",
      "orderDate": "${=datetime(UTC,'yyyy-MM-dd')}"
    },
    "command": "add"
  }
]

My proposal is to use some identifier to distinguish when a user would like to use dynamic values.
${dynamic.input}

Depending on the implementation, it might even be possible to use dynamic keys:
"${$.request.orders.type}": "true"

[FransVanEk]

This is quite interesting but challenging, not per se for the discovery of the dynamic values but for the handling. Currently, the object being handled is the starting point for the values. What would be the starting point for an object with dynamic functions?

Take this command:

  {
    "path": "$.sample.demo",
    "value": "=partial(@.b,@.c.d)",
    "command": "set"
  }

It uses the @ sign to indicate that it is from this level onwards. What would we take for the starting point when having this function in a complex object? What makes sense for the user?