A flow maybe runs under some context. for example, delete-user-flow is for deleting a specific user. the flow function must know the id of that user.
I can let the user pass that data through the action under a specific property: custom-user-data: {..userId:"1",..} but maybe there is a need for something better.
What if a flow function gathers an important information which is required to run the second flow in that workflow? is there any use case to this scenario? if yes, then a workflow is no longer a composition of independent flows. and I should give away to the user have a state between flows under the same workflow. (it sounds like a mass we have in world object in cucumber to pass data between step definitions.)
stavalfi
commented
5 years ago
A flow maybe runs under some context. for example, delete-user-flow is for deleting a specific user. the flow function must know the id of that user.
I can let the user pass that data through the action under a specific property:
custom-user-data: {..userId:"1",..}but maybe there is a need for something better.What if a flow function gathers an important information which is required to run the second flow in that workflow? is there any use case to this scenario? if yes, then a workflow is no longer a composition of independent flows. and I should give away to the user have a state between flows under the same workflow. (it sounds like a mass we have in world object in cucumber to pass data between step definitions.)