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
{{ message }}
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.
Basically, if the conditional field is anything other than a blank string, the step will run. This allows for using the existing templating support (#23) to decide if a step should run.
We'd probably also want to add a Skipped state to the existing step states enum, to make it clear if a step ran or not.
But again, this is very preliminary, we'll see if this really makes things easier, instead of too complex to work with.
To give one example that I came across (with some fictional details):
A task takes a variable X, that variable can be a URL to either a post, or a user page
if it's a user page, fetch the url to the latest post, then go to step 3, otherwise skip this step
fetch the post details
The text was updated successfully, but these errors were encountered:
I haven't thought this through yet, but I've come across some real-world cases that would've benefited from conditional steps.
It would add more complexity to the system, so it's still debatable if the trade-offs are worth it.
As for if we were to do this, the cases I've seen require some way to determine "if the output of step A matches value B, then run this step".
So something like:
Basically, if the
conditional
field is anything other than a blank string, the step will run. This allows for using the existing templating support (#23) to decide if a step should run.We'd probably also want to add a
Skipped
state to the existing step states enum, to make it clear if a step ran or not.But again, this is very preliminary, we'll see if this really makes things easier, instead of too complex to work with.
To give one example that I came across (with some fictional details):
X
, that variable can be a URL to either a post, or a user pageThe text was updated successfully, but these errors were encountered: