search

JonathanKhooTY / pe

0 stars 0 forks source link

A "1 " with spacing is considered as a wrong input at menu selection page #4

Open JonathanKhooTY opened 3 years ago

JonathanKhooTY commented 3 years ago

Users may sometimes accidentally hit the spacebar, and it does not show up clearly in Command Prompt. Hence it is not registered as a valid index despite appearing so to the user. Users unfamiliar with the logic of the app not recognizing spaces as a valid input may be confused. Consider trimming input.

Screenshot was taken at menu selection page.

image.png

nus-pe-bot commented 3 years ago

Team's Response

No response provided.

The 'Original' Bug

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

Command with additional spacing at end is not recognized as valid

Users may sometimes accidentally hit the spacebar, and it does not show up clearly in Command Prompt. Hence it is not registered as a valid index despite appearing so to the user. Users unfamiliar with the logic of the app not recognizing spaces as a valid input may be confused. Consider trimming input.

Screenshot was taken at "view store" page.

image.png

[original: nus-cs2113-AY2021S2/pe-interim#653] [original labels: severity.Medium type.FeatureFlaw]

Their Response to the 'Original' Bug

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

As stated in the user guide, there are no spaces required behind the command.

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: No mention of command usage (Selecting menu number) in UG in this instance, and no mention that having blank spaces before/after is not allowed.

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: No mention of command usage (Selecting menu number) in UG in this instance, and no mention that having blank spaces before/after is not allowed.