nus-pe-bot
commented
1 year ago Team's Response
The UG has stated that command names and prefixes are case-sensitive. However, this is not as important because as fast-typist, it is unlikely that they would capitalise their commands as that would only add more time. Thus, this is NotInScope as it is specified in the UG and rectifying it is less important than the work that has already been done as it's not as easy as it seems as per the definition of NotInScope.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
Currently commands are case sensitive, ie.: "Customer edit" will throw an error. Might be good to make them case-insensitive since likely that users might not consider this to be an issue while using the app, so they will likely be confused as to why the command is not working.