Closed dlongley closed 1 year ago
We might just want to enable steps to be templated generally -- to allow for template variables anywhere in the step.
We can perhaps make steps templates in a backwards compatible way by adding a type
-- and if it's set to jsonata
or another template type then the template
property would also be present with the template information for evaluating the actual step (processing the template against the exchange's variables) later when the step is needed.
Addressed by #39.
Right now, exchanger configs include steps with VPRs that are always the same for every exchange. We might want to enable using templates to generate these VPRs so that exchange variables could be used to more flexibly populate the VPRs as needed, enabling more use cases.