Delete 'Name' Command causes wrong user to be deleted when duplicates are present

[nus-pe-bot]

Description:
When the delete command is used (where a Name is supplied as the parameter), and when 2 different users have the same name but are in different case ('John DoE' and 'John Doe'), the app deletes one of the users but not the other.

Steps to reproduce:

1. Type command: add n/John Doe p/98765432 e/johnd@example.com a/John street, block 123, #01-01
2. Type command: add n/John DoE p/9123456 e/differentJohn@example.com a/John street, block 123, #01-01

3. Type command: delete john doe

Expected: The system throws an error, indicating that there are 2 possible matches (when case insensitive). Ideally, the deletion is rejected, so as to prevent data lost about the wrong 'john' (i.e. the one who should not have been deleted).

Actual: The system deletes one John, while leaving the other present.

Problematic behaviour: All data about the 'wrong' John is lost, which can be very damaging to businesses.

Ways to improve:

• Ensure that if multiple users with the same names are detected, the deletion is prevented, and users are forced to do deletion via indexes instead.

---

_{[original: nus-cs2103-AY2425S1/pe-interim#11] [original labels: severity.Medium type.FunctionalityBug]}

[engyuhan]

Team's Response

Duplicate of #1322

Both bugs are caused by the same defect: improper duplicate detection with the add command. If the add command is fixed, this bug would also be fixed, since there will not be 2 different users with duplicate names anyways. Since both bugs are caused by the same defect and cannot be independently fixed, there are duplicate bugs.

Duplicate status (if any):

Duplicate of #1322