Open KhoonSun47 opened 4 months ago
Thanks for raising this issue, indeed it can be improved further in future enhancements.
Team chose [response.NotInScope
]
Reason for disagreement: I disagree with the decision that this response is "response.NotInScope," and I believe that it should be "response.Accepted" instead.
This feature could be enhanced significantly from the user's perspective with minimal additional effort.
The website already acknowledges the bugs related to duplicate detection, emphasising that exact matches are insufficient and suggesting that warnings for near matches would improve user decision-making.

Steps to reproduce:
Actual Output: Step 1: Adding a person named called "John Doe"![image.png](https://raw.githubusercontent.com/KhoonSun47/pe/main/files/cfc1967d-4ce5-48f9-88de-5bb727da89f4.png)
Step 2: Adding a person named called "John Doe"![image.png](https://raw.githubusercontent.com/KhoonSun47/pe/main/files/97222c23-62ca-4b19-90bf-764f96a2f301.png)
Expected Output:
Suggestion: I believe that should ignore the whitespace in between the names.