search

Aung-Phone-Naing / pe

0 stars 0 forks source link

Unable to handle commands with capitalized inputs #2

Open Aung-Phone-Naing opened 1 year ago

Aung-Phone-Naing commented 1 year ago

As shown in the image below, when the input is capitalized, the app is unable to take in the description.

image.png

nus-pe-bot commented 1 year ago

Team's Response

Hi, thanks for reporting the issue. Please note our application does not accept commands in upper case or a mix of both cases. The same can be found in the usage and example of the commands in our User Guide.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

[Parser] Lower and upper cases

Parser is unable to take in commands that are not the exact match in terms of casing

image.png

[original: nus-cs2113-AY2223S2/pe-interim#1891] [original labels: severity.Low type.FeatureFlaw]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

Hi, thanks for reporting the issue. Please note our application does not accept commands in upper case or a mix of both cases. The same can be found in the usage and example of the commands in our User Guide.

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: [replace this with your explanation]

## :question: Issue response Team chose [`response.Rejected`] - [x] I disagree **Reason for disagreement:** The UG and DG do not clearly state that people are unable to input both upper case or a mix of both cases as shown in the pictures below. This may lead to users believing that the app is not case sensitive and encounter the bug when they accidentally or intentionally put the command words in upper or mixed case. This then remains to be a valid bug that needs to be resolved. ![image.png](https://raw.githubusercontent.com/Aung-Phone-Naing/pe/main/files/e768bad7-1e0c-4cd2-b3b8-bb9a2ec94117.png) ![image.png](https://raw.githubusercontent.com/Aung-Phone-Naing/pe/main/files/fb7fc485-5489-466a-a540-ab6928895e80.png)
## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.FunctionalityBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** The severity should remain to be a medium as the case sensitivity is an issue that applies to all commands hence this is a flaw that applies to all users. Due to the fact that, users regardless of professional status may encounter this bug when they perhaps have their **capslock** on when typing or mis-clicked the shift key as they type resulting in the input that is not accepted by the app. Once this happens users may be puzzled as to what is wrong with their input as the error message shown above also does not clearly specify to the user on what their error might be, further propagating the issue and making this an occasional inconvenience for all users. This bug applies to both new users and fast typists. Hence this warrants a medium severity as a bug.