Open zuohui48 opened 1 year ago
Thank you for raising this, however, the name feature is intentionally designed to prevent special characters, as almost all of them are by definition, invalid. Let us explain further.
We have given much thought into the design of our names and followed the "Name" class implementation of AB3 which similarly disallows special characters like "/" slashes in names.
The reason why we did not allow special names in "s/o" because allowing the special character "/" would allow actual invalid names like "bob ////// tom" which would be a larger feature flaw.
Furthermore, we belive this is more of a preference issue, to provide more convenience for users by allowing shortcuts. This is because "s/o" is short form for "son of" which is a valid input in name, hence users can still represent all of their full names in our address book, as seen below.
We appreciate your suggestion but we disagree this is a medium feature flaw, thank you.
Team chose [response.Rejected
]
Reason for disagreement: Hi, I completely understand where you are coming from. I would agree if the use of special characters in names makes it difficult for the input to be parsed. However, disallowing s/o, which is part of a person's legal name, will cause inconvenience to the user as he is unable to enter his legal name. Below is the screenshot taken from the course website regarding the use of symbols in input values.
Thank you.
I am unable to enter a valid Indian name which consist of S/O with the add command.
Steps to reproduce: