soc-se-bot
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
Thank you for your bug report!
However, we do not think having case-insensitive commands is optimizing for fast typists, as fast typists are accurate as well. We designed our commands with typists in mind, which is why we only use lower-case characters for commands so users do not have to enter or hold an extra key while entering commands therefore providing a better experience for typists.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
Description Set the context.
Long commands (such as add, schedule, potentially edit and tag) and case-sensitivity makes the command(s) not optimised for fast-typists. Stated at the introduction of User Guide that application is optimized for typists.
Expected behaviour
Commands are case-insensitive to optimize it for fast typists.
Actual behaviour
Commands are case sensitive which could pose as an obstacle for fast typists.