Inefficient CLI design

[yiyang74]

Making all the commands case sensitive in nature hinders the slows down usage of a CLI app where users have to worry about case-sensitivity. For example, CS1010 and cs1010 mean the same course, there is no need for it to be case sensitive.

[soc-se-bot]

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

Team's Response

While some commands do allow for non-case sensitive commands, not every command had the feature implemented due to time issues. However, we believe this is acceptable as the CLI-First constraint is only a recommendation, not a requirement:

Items for the Tester to Verify

❓ Issue response

Team chose [response.NotInScope]

• I disagree

Reason for disagreement: Case sensitivity for course module codes does not matter in real world. For example, NUSMods is not case sensitive. Therefore, the app shouldn't be case sensitive as well. This is a bug.

---

❓ Issue severity

Team chose [severity.Low]
Originally [severity.Medium]

• I disagree

Reason for disagreement: This can be low if there was consistency between commands, for example, if the choice was to make any command case sensitive, all commands should be all case sensitive, vice versa. The discrepancy will require the users to keep track of which commands are case sensitive while which is not which causes occasional inconvenience to users.

---