Explanation

This rule detects condition nodes without a label. Every condition node and edge coming from a condition node should be labeled with the condition or alternative respectively in order to have readable and maintainable flows.  

We estimate that resolving this issue will on average take 5 minutes.

Possible improvement

Condition nodes without a label have a negative impact on the readability and maintainability of the flows since all nodes in the flow should have descriptive names. In case of the condition node the main node should pose a question, while every alternative edge should pose an answer to that question. 

Example

This flow contains a condition node where no label is present. It is unclear what kind of decision is represented by the node.

This flow results in the following code smell: