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
Please describe what you would like to see in this project
With a standard expression, truthiness can be implied by simply reaching a particular node state in a workflow:
!expr $.steps.example.outputs
However, when a logical AND or OR is added to the expression, the expectation is explicit boolean values on each side. Because of this, it is not currently possible to evaluate multiple node states in an expression. This does not work:
Also, the stringToBool() function does not work in this case since it will only convert explicitly truthy string values like true, false, y, n, 1, 0, etc. So this also does not work:
Please describe what you would like to see in this project
With a standard expression, truthiness can be implied by simply reaching a particular node state in a workflow:
However, when a logical AND or OR is added to the expression, the expectation is explicit boolean values on each side. Because of this, it is not currently possible to evaluate multiple node states in an expression. This does not work:
Also, the
stringToBool()
function does not work in this case since it will only convert explicitly truthy string values like true, false, y, n, 1, 0, etc. So this also does not work:Please describe your use case
This is particularly important when using a
wait_for
in a workflow step for explicit dependencies and serialization.The text was updated successfully, but these errors were encountered: