Bug: The name parameter is not able to save names with "/" character

[jeronkk]

Description:

When I tried to edit a name to include a common part of some Indian names like "S/O", the app rejects it and says that an error Names should only contain alphanumeric characters and spaces, and it should not be blank. I think it should allow users to key in names with unicode characters so that certain special characters like "Nguyễn" can also me keyed into the list.

Steps to reproduce:

1. Enter the below command.

edit 1 n/John S/O Doe

2. The error message Names should only contain alphanumeric characters and spaces, and it should not be blank should show.

[nus-se-bot]

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

Team's Response

Thank you for the bug report, however this bug was mentioned under "Planned Enhancements" hence this bug is rejected.

From DG under planned enhancements section:

Furthermore, from the course website for bugs reported under the Planned Enhancements section:

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Unable to add contact with names containing symbols such as @ or /

Steps To Reproduce

• Try to add a contact by the following command add n/Ravi s/o Kumar p/98765432 e/johnd@example.com a/John street, block 123, #01-01 r/Vendor

Expected

• I should be able to add since it is a valid name as s/o usually means "son of" in Indian terms.

Actual

• The addition of the contact was not allowed since it was not alphanumeric.

Rationale
It is common for Indian names to have / or @ and if a vendor cannot be added just because his name contained @ or /, it should be considered a feature flaw.

---

_{[original: nus-cs2103-AY2425S2/pe-interim#653] [original labels: severity.Low type.FeatureFlaw]}

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

Thank you for the bug report, however this bug was mentioned under "Planned Enhancements" hence this bug is rejected.

From DG under planned enhancements section:

Furthermore, from the course website for bugs reported under the Planned Enhancements section:

Items for the Tester to Verify

❓ Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

• I disagree

Reason for disagreement: [replace this with your explanation]

---

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: [replace this with your explanation]

---