Open JoelHo opened 3 years ago
We considered that it might be cluttering. However, we might consider trying to simplify the workflow in the future. For now, we did not find a way to work around this in a CLI-based app.
Team chose [response.NotInScope
]
Reason for disagreement: In my opinion, I don't think that an alternative view would be cluttering.
For example, they could have 3 columns: persons, sessions, and students in each session. However, the team has decided to keep with this system of viewing sessions via a command, which makes the workflow quite troublesome to work with.
Currently, tutors are shown in a session by
t/1
for example. However, to figure out who this is afterview_session
, I need to go back tolist persons
and correlate this to the tutor, which is inconvenient and unintuitive.