Add ability to *require* subflow env variable before deploy (like real nodes)

Just a simple checkbox under each env property in properties editor, which when checked, would require these fields not be left empty before deploying.

For now my workaround is checking for these fields to be filled in and throwing an node.error when they're empty, but this could be avoided if the flows were never allowed to be deployed with the subflow config in an error state.

EDIT: updated image for clarification- sorry I didn't spend enough time to align the label correctly.

To be clear, we never prevent a deploy, but will warn the user there are misconfigured nodes.

Adding validation options to the subflow properties would be a useful feature. Have added to the backlog.

Yes sorry for the the muddy wording- do not prevent a deploy but notify the user of an error before deploy. Thank you.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.