Open Fallman2 opened 11 months ago
No details provided by team.
[The team marked this bug as a duplicate of the following bug]
Name does not support s/o
For Indian names, it is possible that the legal names include the "/" character. As such, one should make a concession for this case where legal Indian names will be allowed
[original: nus-cs2103-AY2324S1/pe-interim#4794] [original labels: type.FunctionalityBug severity.VeryLow]
[This is the team's response to the above 'original' bug]
In the app, there is no requirement for a legal name as the names are used purely to track and distinguish tutors.
In fact, enforcing the strict use of legal names would not allow people of the same name to be in the app (so users need a way to differentiate their names).
In the example raised about legal Indian names, users can easily solve the problem either by using so instead of s/o or not including the last part of the tutor's name.
Additionally, this was an intentional design choice. You may read more in the DG > Add tutor feature > Design Rationale > Aspect: Tutor name restrictions
Including too many special characters can lead to outcomes like erroneous parsing and it becomes more difficult for users to later retrieve this person using find commands.
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
Reason for disagreement: [replace this with your explanation]
When entering a new tutor, an error is shown when the "/" key is attempted to be used in the name field. Considering that this software is to be used by tuition centres who employ tutors, the legal name is expected to be used as the name. Given that "s/o" is a relatively common term used in names, the "/" character should be accepted.
Steps to reproduce: Enter an add-t command with a / in the name field. Command input:
add-t n/John s/o Doe p/98765432 e/johnd@example.com