Open ZiliaAJY opened 1 week ago
Thanks for raising this issue. Firstly, keeping the activation bar continuous reflects the consistent flow of the process. It shows that the method remains active throughout the conditional checks, which is accurate as the conditions are evaluated sequentially within a single ongoing operation. Secondly, most of the time, the activation bar remains continuous because the process flows without interruptions. This reflects the typical user experience where inputs are usually valid and the process completes smoothly. This approach does not hinder developers from understanding the process. It is very clear that if the correct conditions are met, the function exits, as indicated by the dotted return call arrow. This visual cue effectively communicates the point where the method stops due to a rare exceptional condition.
Team chose [response.Rejected
]
Reason for disagreement: [replace this with your explanation]
The activity bar should be cut off when it is returned if one of the conditions are met. The cutoff between the bars are to be joined by the lifeline.