nus-se-script
commented
1 year ago Team's Response
We recognise this issue is present, however due to the usage of '/' to identify tokenisers, it would be buggy to allow it. '/' are usually used to represent shortcases in names. Therefore, it will be intuitive for the user to spell out the entire name instead. For example: john son of asd. This is therefore an issue that will only cause minor inconveniences in rare scenarios and should only warrant a severity of LOW
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Add command: name field does not accept names with s/o in them
add n/Lewis s/o Hamilton p/87438807 e/alexyeoh@example.com pos/Student a/Blk 30Geylang Street 29, #06-40 t/CS2103T-T17
[original: nus-cs2103-AY2223S1/pe-interim#1251] [original labels: type.FeatureFlaw severity.Low]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
No details provided by team.
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)
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
:question: Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
- [x] I disagree
Reason for disagreement: Features that work as specified by the UG but should have been designed to work differently (from the end-user's point of view) fall in this category too. - Definition of feature flaw
It is a feature flaw because there are quite a number of students with s/o in their names and it will cause occasional inconvenience to these users and as such although they are able to work around it, it should have been designed to work differently.
Bug Report
What Happened:
Steps to reproduce:
add n/john s/o asd p/123123123123 e/asd@asd.com pos/Professor a/123 t/CS2103T-CS2103TScreenshots
![Uploading Screenshot 2022-11-11 at 4.35.50 PM.png...]