soc-pe-bot
commented
6 months ago Team's Response
This is not a bug. The commands being case sensitive is a design choice to prevent incorrect command from being parsed. It also allows our app to be more scalable if we decide to have more varied command case in the future.
The only scenario where the proposed change is beneficial is specifically when the user capitalizes specific characters in the command (e.g. upDaTe), but this is extremely unlikely. Therefore, we reject this bug.
This issue is also targeted towards a feature of the app, so we have changed the tag to feature flaw.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.FunctionalityBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
Description:
Steps to reproduce:
Expected behaviour: Add command should execute correctly
Actual behaviour: Command is not recognized by the app.
Notes: Since typos can happen, there may be a case where the user accidentally capitalizes one random letter or more in the command word. However, since this does not change the semantic meaning of the command, it should be accepted since there is no ambiguity resulting from capitalizing one letter in the command word itself.