Command words are unnecessarily case-sensitive

[nus-se-script]

Description

The command words are unnecessarily case-sensitive which may affect the efficiency of the user. For e.g. ADD and add should not serve different purposes.

Steps to reproduce

1. input ADD n/John Lee p/98765432 e/johnd@example.com m/Computer Science

Expected

Person should be added successfully.

Actual

The application recognises it as an invalid command.

Screenshots

---

_{[original: nus-cs2103-AY2324S2/pe-interim#2205] [original labels: severity.Low type.FeatureFlaw]}

[evedaktyl]

Team's Response

Thank you for pointing this out. We do note that it may be considered feature flaw if the command word or input is unnecessarily case-sensitive.

However, based on the argument of efficiency, as brought up in the bug report, we feel that typing out the command word in lowercase is much more efficient than any other method, e.g. 'Add' or 'ADD'. Hence, it can be seen as unnecessary to make the command word case-insensitive, to accommodate for more inefficient methods. Making it case-insensitive will also require there to be additional notes about case usage in the documentation, complicating the command guide.

Thus, since our current implementation with the command word being case sensitive has little implications on efficiency and can be supported by a cleaner, simpler command guide in the UG, we feel that it is justified to leave it as such.

Duplicate status (if any):

--