Open jiahui0309 opened 7 months ago
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.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
steps:
Add
expected: should also accept as command words should not be case sensitive