Input parameters do not support lambda expressions

Hi there,

our team is having lots of unnecessary lambda expressions pre and post workers execution. Most of which are checking for null values or exist checks increasing the size of the workflows drastically.

Our first goal, was to do something like this:

"inputParameters":{
        "pn": "${ ${w1.output.nb} == null ?  null : \"w1.output.nb\"},
        "http_request": {
                 "uri": "http://someEndPoint/user",
                 "method": "POST",
                 "accept": "application/json",
                 "body": "{ \"username\":  \"w1.output.username\" , \"pn\": $.pn}
        }
 },

Q:

1. Is there a way to do what I’ve attempted to do with pn without using lambda workers?
2. If what I am attempting to do is not supported is there a plan of adding feature similar to what I’ve described in the next release?
3. If this is something that you guys are interested in but don’t find super essential. Would you like our team to take it on?

Thank you!

[apanicker-nflx]

1. Is there a way to do what I’ve attempted to do with pn without using lambda workers?

Currently, there isn’t a way to achieve this without using lambda tasks.

1. If what I am attempting to do is not supported is there a plan of adding feature similar to what I’ve described in the next release?

This is not supported currently, but we feel that this would be a great addition to the project. Unfortunately, we will not be able to work on adding this feature.

1. If this is something that you guys are interested in but don’t find super essential. Would you like our team to take it on?

We would greatly appreciate it if your team can contribute this feature. I am sure this would benefit other users of Conductor as well.

[github-actions[bot]]

This issue was closed, because it has been stalled for 7 days with no activity.