Open atmh opened 2 years ago
We want to give the user more flexibility, and so our feature does not enforce duplication detection. Hence, we don't think this is a bug.
Team chose [response.Rejected
]
Reason for disagreement: The dev team claims that they do NOT enforce duplicate detection. However, there is clearly some form of duplicate detection. Steps to reproduce:
Evidently, there IS duplicate detection. To reiterate my point, in reality "Damith" and "damith" is highly likely to be the same person. However, the app treats them as different individuals. The limitations of this feature is not made clear to the users. It was never stated how duplicate detection works, and this is a flaw in itself.
This bug report follow closely to the Bugs related to duplicate detection of the CS2103T website. Combined with the fact that how duplicate detection works is never mentioned, this should be at minimum a severity.low bug or higher.
Steps to reproduce:
add n/Damith p/99998888 e/damith@damith.com a/Blk 123 i/package 1
add n/damith p/99998888 e/damith@damith.com a/Blk 123 i/package 1
Expected: Error message "This client already exists in the address book"
Actual: Command executed successfully.
Reason: In reality "Damith" and "damith" is highly likely to be the same person. The address book should recognize that they are similar and ideally throw an error message, or give a warning in such near match cases.
From CS2103T website: