menu command is case-sensitive, but not stated in UG

[nus-pe-bot]

for all other commands, it is clear whether or not it is case sensitive or not. however, for the menu command, it is not clear. if nothing is stated, the user assumes it is case insensitive. thus, the MENU input should result in a menu option. but it does not. steps to recreate: MENU [severity is high, as a command is inaccessible]

---

_{[original: nus-cs2113-AY2324S2/pe-interim#2259] [original labels: type.FunctionalityBug severity.High]}

[itsmejr257]

Team's Response

Hi. Thank you for your suggestion and i do believe that the indication of the command being case-sensitive in the UG / making the command case insensitive can be considered. However, this is of lower priority than the work already done in v2.1. This is due to multiple reasons :

1. Typing MENU and getting an error message (Invalid Command) is an expected output. The command to be used for the menu feature is stated in the UG by calling the command menu not MENU
2. I would also qualify this Severity as a Low instead of High as this flaw is unlikely to affect normal operations of the product. When booting up BudgetBuddy, the welcome message always informs the user that they can access the menu by typing menu. Hence, a user stuck at typing MENU wondering why they cant access the menu would appear only in very rare situations, and causes a minor inconvenience only. Given that every single boot of BudgetBuddy provides the message please type "menu INDEX"and type "menu", i do not believe that a case sensitive command would make the product unusable for most users.

Therefore, the implementation of making this command case insensitive was of a lower priority than the features implemented in v2.1, and i have change the severity to Low and set the response as NotInScope

Duplicate status (if any):

--