search

Jayne1010 / pe

0 stars 0 forks source link

Wrong error message for upper case commands #2

Open Jayne1010 opened 6 months ago

Jayne1010 commented 6 months ago

Screenshot 2024-04-19 at 4.14.56 PM.png

Commands should be case in-sensitive and this may bring about inconvenience to the users if they accidentally type the command in upper case but the error message shows an unknown command.

nus-pe-bot commented 6 months ago

Team's Response

UG should have clearly mentioned the case-sensitivity of all command words.

Items for the Tester to Verify

:question: Issue type

Team chose [type.DocumentationBug] Originally [type.FeatureFlaw]

Reason for disagreement: Screenshot 2024-04-23 at 10.42.08 AM.png

In real world context, users will use upper case command keyword and it is only natural to accept them.

## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Low`] - [x] I disagree **Reason for disagreement:** ![Screenshot 2024-04-23 at 10.40.35 AM.png](https://raw.githubusercontent.com/Jayne1010/pe/main/files/24259d7d-fe7e-4d7c-8147-3e341297ab1e.png) Definitely affects the normal operation of the product as the command does not work. Not a cosmetic issue imo.