Open juliusgambe opened 9 months ago
We recognise this is a flaw in our features, but this would be an issue for a small portion of users only, as people with S/O in their names (or other special characters) may be saved and identified using the other parts of their name. This is especially true in a student-targeted app where students are unlikely to save the full legal name of their friends in their contact list. Thus, rectifying this issue is not as important (based on the effort considerations, since it might be harder to change the other functions that rely on the name of the contacts, such as Find Person) as the work that has been done already.
As such, we are categorising this as a featureflaw that is out of scope because from a certain point of view, it could be a suboptimal design. 1. The UG specifies this constraint. 2. When the user attempts to add a second person with the same name, the software gives a suitable error message, this meets the requirements for an out of scope response.
Thank you so much for the feedback!
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
Bug Report:
Unable to key in certain special characters such as
/
where names such asJohn s/o Doe
exist.Expected Output
Successfully add the name in.
Actual Output
Steps To Reproduce
add n/Johns/oDoe p/98765432 e/johnd@example.com g/CS2103T
Other Information
System Information