Given the context of managing potential hires and employees, it is highly possible that they could have the same name.
The system currently blocks the adding of an employee with the same name (even though the rest of the fields are different) and displays a warning This person already exists in the address book. This could have been handled with warnings, such as duplicate entry alerts. This blocking behaviour can disrupt workflow unnecessarily when duplicates might be intentional (e.g., multiple employees with the same name). The current implementation makes adding those with the same name impossible.
Given the context of managing potential hires and employees, it is highly possible that they could have the same name. The system currently blocks the adding of an employee with the same name (even though the rest of the fields are different) and displays a warning
This person already exists in the address book
. This could have been handled with warnings, such as duplicate entry alerts. This blocking behaviour can disrupt workflow unnecessarily when duplicates might be intentional (e.g., multiple employees with the same name). The current implementation makes adding those with the same name impossible.[original: nus-cs2103-AY2425S1/pe-interim#581] [original labels: type.FeatureFlaw severity.High]