search

saintzaw / pe

0 stars 0 forks source link

UG does not mention whether UID is case-sensitive #10

Open saintzaw opened 1 year ago

saintzaw commented 1 year ago

As a user, I only find out that UID is case-sensitive for the remove and mark commands etc when I am using the app and get an error message. At the same time, the UID happens to not be case-sensitive when I use the find command. This is confusing and inconvenient for me as a user and if the app accepts lowercase alphabets for the UID for certain commands (like find) ,the UG should at least specify whether the UID is case-sensitive and for which commands

nus-se-script commented 1 year ago

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

Team's Response

The case-sensitive issue arose from the lack of consistency when developing the features. By right the UID is designed to be case-sensitive by nature (hence the capital letters in the UID), however not implementing it consistently lead to readers/users assuming that there is missing documentation.

The 'Original' Bug

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

Remove and mark command are case-sensitive but find command is not

Untitled4.png I'm able to find an existing uid by substituting the uppercase alphabets for lowercase ones

Untitled5.png

However, I'm unable to do the same for the remove command, which only works if the alphabets in the uid are in uppercase.

This is inconvenient for users who may want to use lowercase alphabets only and are sometimes accepted and rejected at other times while using the app

Untitled6.png

It's also case-sensitive for mark.

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

Their Response to the 'Original' Bug

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

Accepted. Find, Remove and Mark/Unmark commands should have been standardised for case-sensitivity.

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 reason]

## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.DocumentationBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your reason]