search

YongbinWang / pe

0 stars 0 forks source link

Delimiter prompt such as /t /n is not case-insensitive #4

Open YongbinWang opened 1 year ago

YongbinWang commented 1 year ago

Describe the bug

This bug is similar to the command name being case-insensitive, but fixing it will not be the same thus it has been added. Delimiter prompt is not case-insensitive which might affect the user experience.

To Reproduce

Steps to reproduce the behavior:

  1. Create test 3 file txt
  2. add N/test 3 t/SORTING i/6

Expected

Expected file to be successfully added into SORTING

Actual

Exception is thrown and file is not successfully added.

Screenshots

image.png

nus-pe-bot commented 1 year ago

Team's Response

This is the intended behavior of our application. Not following the syntax strictly leads to an invalid command error message.

image.png

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: I argue that this should not be rejected. This is a very useful feature to have for better user experience and should at least be classified as NotInScope. It seems that the team is trying to use a one sentence catch-all in their user guide to address most, if not all of the issues that might be raised during the practical exam regarding their command syntax. Most users will love the flexibility and robustness of such a feature.

This is a minor improvement that the team can perform and the severity given is low, yet they chose to reject it.