You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A Flow Control operation, similar to Fork, but with the goal of carrying out the subsequent operations in the recipe on the same input, rather than chaining them together and operating on the output of the previous operation as normal.
Example
Input
Test
Recipe
Branch (or some other more suitable name)
To Hex
To Base64
To Binary
I don't really like the name 'Branch' because it's too close to 'Fork' and would lead to confusion, but I can't think of a more suitable name at the moment.
The text was updated successfully, but these errors were encountered:
I've made a Pull Request (PR) with a simple implementation of this functionality. Would love more use-cases, examples, etc. as I believe the operation as I've implemented it is fragile... that is, I'm not sure it will accomplish all that people want it to accomplish given a more diverse set of input(s). It does produce the correct output given the input listed above, however.
Also, I've called it "Disjoin" as that to me sounds "far enough away" from the term "Fork", (versus the currently suggested "Branch") though, I was also considering the following:
Summary
A Flow Control operation, similar to Fork, but with the goal of carrying out the subsequent operations in the recipe on the same input, rather than chaining them together and operating on the output of the previous operation as normal.
Example
Input
Recipe
Output
I don't really like the name 'Branch' because it's too close to 'Fork' and would lead to confusion, but I can't think of a more suitable name at the moment.
The text was updated successfully, but these errors were encountered: