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
In the most case it makes sense to convert string to numeric, if this conversion is doable. In this case expression will work with them as numeric when possible. For example, the expression: "{val1} + {val2}", where val1: "1" and val2: "2" will return 3.
However, in some cases developers need to have these variables as strings and want to have the result "12".
To support both scenarios, we are adding the following '#' variable prefix to disable the conversion.
"{val1} + {val2}" will return 3 and "{#val1} + {#val2}" will return "12".
The text was updated successfully, but these errors were encountered:
andrewtelnov
changed the title
Disable convertion variable in expression from string to numeric or boolean
Optionally disable convertion variable in expression from string to numeric or boolean
Sep 9, 2020
andrewtelnov
changed the title
Optionally disable convertion variable in expression from string to numeric or boolean
Optionally disable conversion variable in expression from string to numeric or boolean
Sep 9, 2020
In the most case it makes sense to convert string to numeric, if this conversion is doable. In this case expression will work with them as numeric when possible. For example, the expression: "{val1} + {val2}", where val1: "1" and val2: "2" will return 3.
However, in some cases developers need to have these variables as strings and want to have the result "12".
To support both scenarios, we are adding the following '#' variable prefix to disable the conversion.
"{val1} + {val2}" will return 3 and "{#val1} + {#val2}" will return "12".
The text was updated successfully, but these errors were encountered: