Signal url couldnt be an expression #1289
Replies: 4 comments
-
Hi @rezabashiri I'm sorry but I'm not really sure I understand your question, or maybe you trying to suggest a feature. (I edited your code sample - on Github you can use three back-ticks: ``` to mark a code-block) |
Beta Was this translation helpful? Give feedback.
-
I think I do understand actually. It looks like @rezabashiri wants to evaluate the signal provided as workflow input as well:
However, the suggested change will require the input to always be a valid JavaScript expression. Additionally, evaluating workflow input like this in a given activity seems too arbitrary for my sanity. @rezabashiri Perhaps if you would share with us your use case, we can think of a better solution if we need one? |
Beta Was this translation helpful? Give feedback.
-
@sfmskywalker yeah this is some kinda enhancement, I did a small hack to support both type of literal and javascript expressions `
|
Beta Was this translation helpful? Give feedback.
-
With Elsa 2, it is now possible to define dynamically evaluated signal names. A sample of this can be found in this guide. |
Beta Was this translation helpful? Give feedback.
-
At 'Signal' activity, elsa just get variable and compare it by the signal property, but it doesn't respect type signal, it could be java expression so I suggest an easy correction tp overcome this kind of lacking
Beta Was this translation helpful? Give feedback.
All reactions