soc-se-bot
commented
6 months ago Team's Response
We explained this in the user guide. We think that the design choice is justified.
The command name and tag is case-sensitive, following tradition of bash shell commands. Nevertheless, all command names are in lowercase, and typing lowercase characters is faster than typing uppercase characters.
Similar to #2541 though, it's possible to have a configuration option to configure this.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
Command argument prefixes, such as "e/" are case-sensitive. This means that the app will not recognise prefixes such as "E/". This adds unnecessary inconvenience for users.
Note: error message is wrong as said in #5.