You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It would be really nice if we could have the ability to nest expressions in each other. This is especially nice for when dealing with complex JSON structures in the data for Player.
Currently that expression fails purely due to what seems like string splitting on the special characters, @, {{}} and [].
Describe the solution you'd like
For the string splitting logic to be aware of possible nested occurrences of special characters, and to deal with them appropriately. It should probably work "backwards" - Where the deepest expression is ran first, so that the returned instance of that expression can be fed into the parent expression - Unless the expression parser itself can deal with this is in the translation layer.
Cheers!
The text was updated successfully, but these errors were encountered:
This should actually be supported today (a good push for us to update the docs to make this clearer)
Once you're inside of an expression block (the contents wrapped by @[]@), you're free to use and nest any number of expression calls. In your example, it would be something like:
This should actually be supported today (a good push for us to update the docs to make this clearer)
Once you're inside of an expression block (the contents wrapped by @[]@), you're free to use and nest any number of expression calls. In your example, it would be something like:
Is your feature request related to a problem? Please describe.
It would be really nice if we could have the ability to nest expressions in each other. This is especially nice for when dealing with complex JSON structures in the
data
for Player.An example of this would be:
Currently that expression fails purely due to what seems like string splitting on the special characters,
@
,{{}}
and[]
.Describe the solution you'd like
For the string splitting logic to be aware of possible nested occurrences of special characters, and to deal with them appropriately. It should probably work "backwards" - Where the deepest expression is ran first, so that the returned instance of that expression can be fed into the parent expression - Unless the expression parser itself can deal with this is in the translation layer.
Cheers!
The text was updated successfully, but these errors were encountered: