Open Wincenttjoi opened 4 years ago
Hi, thanks for your report! Our diagram abstracts out functionality of the review mode by showing an example of one key press input. Hence, we did not feel the need to show the full loop.
For reference, we modelled the diagram based on the workflow of a single key event in our switch case code which also explains the diamonds:
Team chose [response.Rejected
]
Reason for disagreement: Thank you so much for providing the code snippet which explains why the different scenarios are not interlinked with one another.
You can refer to the diagram below, hope this provides clarify to the point im trying to make.
Team chose [severity.Low
]
Originally [severity.Medium
]
Reason for disagreement: [replace this with your explanation]
No details provided.
Should there be a loop back if lets say its not at the last question?
Furthermore, instead of having multiple if else, I think it all the different options should branch out from the same diamond, because from that same point, a user can have multiple options (arrow up, down left, right). Down arrow is dependent on result of up first, etc.