nus-pe-script
commented
6 months ago [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
No details provided by team.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
case sensitivity of command words
steps:
- run
Addexpected: should also accept as command words should not be case sensitive
[original: nus-cs2103-AY2324S2/pe-interim#5088] [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 not really a good feature to add, as starting the command with a capital letter is more cumbersome for the user anyway, and does not add any value to the user, unlike in longer commands like
addMeeting, where camelcase clearly indicates that the command is composed of two words, which is a design decision our team made.Suppose that making command words case insensitive would add value for the user. This would require that our entire set of commands be revamped for a minor quality of life improvement, which is not in the scope of v1.4.
In addition, the second point of the following screenshot holds for this case, as case sensitivity is not a feature in the first place and is of a low priority as compared to fixing other serious bugs.
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 reason]
## :question: Issue response Team chose [`response.NotInScope`] - [ ] I disagree **Reason for disagreement:** [replace this with your reason]
Some commands such as addMeeting or editMeeting requires specific uppercase to be input. However, this might significantly slow down the input process as the user need to check for those uppercases. Also, there is no duplicate issue when using "addmeeting" or "editmeeting" or "clientindex" instead. Therefore, this might slow down the user even if they are a fast typer, lowering the values and benefits of the app.