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
#/definitions/waitStep/wait having {"type": "null"} is a bit of an outlier (only one other instance, and its #/definitions/dependsOn).
I'm guessing it is documented because wait step docs explicitly call out null as a value you can use. However, from some light testing, BK is totally fine with other fields being null too!
👋
#/definitions/waitStep/wait
having{"type": "null"}
is a bit of an outlier (only one other instance, and its#/definitions/dependsOn
).I'm guessing it is documented because wait step docs explicitly call out
null
as a value you can use. However, from some light testing, BK is totally fine with other fields beingnull
too!So, curious if, for correctness sake, most fields should be exploded into support
null
, or if for conciseness they shouldn't.The text was updated successfully, but these errors were encountered: