nus-se-bot
commented
2 years ago Team's Response
No details provided by team.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Minor inconvenience to input commands with camel casing for fast typists
For commands that uses camel casing such as
addClient, it would be more convenient if I do not need to use camel casing. For example, as a user who is also a fast typist, it would be more convenient if I could type in the command without needing extra keystroke (eg. pressing caps or holding shift).
[original: nus-cs2103-AY2122S2/pe-interim#3086] [original labels: severity.Low type.FeatureFlaw]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
This is personal preference for different testers. If no camel case is employed, users could say that the commands do not distinguish between words and are unclear as well. Hence, our team chose to use camel case so that it improves the readability of the command.
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Even if readability were an advantage in terms of camel casing, since this is an input that has to be typed by the end-user rather than read, I think the advantage of the reader being able to read something they have typed themselves is overshadowed by the disadvantage of being overly-complicated to type.
As per the module website, commands are judged more on their ease of usage rather than the readability:
:question: Issue severity
Team chose [severity.Low]
Originally [severity.VeryLow]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
In my opinion, 'addclient' and 'addClient' (along with the other camel-case commands) look the same. Since it takes more effort to camel case the command, it could prove an annoyance to users who are using the application extensively. Since there are no commands which are similar, a case-insensitive command parsing would be much more user-friendly.