Fridolín Pokorný

Hi Rathish, excellent! Nice work. Feel free to open a PR in author names. It will be easier for both ends to do a review, test and include changes in...

> Wondering if selinon has plans to integrate jinja2 so users can use templates for variables I'm not sure here. Where these templates would be beneficial? Can you give me...

@bubthegreat sorry for late answer, I somehow missed this. Looking at this - I'm not sure if I follow. I assume the ``cases_worker`` calls a subflow called ``get_cases_task`` (the very...

Hi @nerdvegas, thanks for the explanation. Now I see a real-world use case - it would definitely make sense to provide such functionality. Actually, it would not be that hard...

In that case, I'm probably missing the semantics behind binding - originally, I thought you are looking for a way how to define values specific for tasks directly in the...

``` - from: # null == entire output ``` This looks like a usage of `node_args_from_first` configuration option - see https://selinon.readthedocs.io/en/latest/yaml.html#node-args-from-first As described above, see selinon configuration as a transcript...

A flow is defined as a graph (not limited to acyclic graphs) of tasks which is interpreted based on task success/failure. You can see it as chaining execution of these...

> Are you saying that there will be one instance of sum1 run in flow3, but two in flow4? Yes. In `flow4`, the first `sum1` task will be run after...

BTW you can also do something like: ```yaml flow-definitions: - name: flow5 edges: - from: - render1 to: - sum1 - sum1 - sum1 ``` Which will run 3 times...

> Right, but in flow3, the multiple sum1 references are regarded as the same task? That is the ambiguity I'm referring to. It doesn't seem clear to me that a...