I'm regularly running into the situation where I need the value of an option of an encompassing pipeline in a nested sub-pipeline (a nested p:declare-step). That is not allowed.
However, from what I (and probably others) might expect from other programming languages, access to these options is kind of logical: they're defined before the p:declare-step and so I'm expecting them to be in scope. But alas, they are not. So I have to pass them as option to my nested sub-pipeline (over and over again).
Can we change this scoping in a next version?
I'm regularly running into the situation where I need the value of an option of an encompassing pipeline in a nested sub-pipeline (a nested
p:declare-step). That is not allowed.However, from what I (and probably others) might expect from other programming languages, access to these options is kind of logical: they're defined before the
p:declare-stepand so I'm expecting them to be in scope. But alas, they are not. So I have to pass them as option to my nested sub-pipeline (over and over again).Can we change this scoping in a next version?