Unintuitive command format

[Jxleejiaxin]

I expected that I could navigate to "Groups" and still use find course CS2103 to search within the course list. However, the result is as follows:

If I have to be on the correct page to use the corresponding find command, it might be more intuitive for the group, course, etc specifiers to be dropped and the find command can be used as is.

Edit: As I continued testing the app, this issue can be applied to almost all other commands as well.

[nus-se-bot]

Team's Response

Thank you for the feedback and suggestion!

In the case of intuitiveness, we tested the app while thinking from a general user perspective when using the app. A user can think of the following while using the app: "I add a course CS2103 into the list", "I add a group T15 into the list" etc, hence add course and add group etc seems to be more intuitive for the perspectives respectively.

It is also a specific design for data safety. If a user were to add course on the group page, we can prevent such scenarios by displaying an error message.

As such, we have decided to reject this suggestion.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: To execute these commands, the user already has to input select commands to navigate to the correct page. Hence, I do not agree that this command format is intuitive at all. In fact, with this command, I expected to be able to use the find command anywhere since there is an argument specifying the search field.

For add command, the argument for data safety makes sense. However, I feel it also obstructs the user executing commands on a CLI due to the length of the command.

---