Open WangCheng0116 opened 11 months ago
We believe that this is our check is reasonable enough and this is an edge case that is:
Team chose [response.NotInScope
]
Reason for disagreement: I disagree for the following reasons:
User-Friendly Behavior:
Natural Language Variations:
User Expectations:
Common Data Entry Mistakes:
To add on, upon testing, we can discover that the application successfully trims the whitespace before and after the name field, indicating that the dev team has made such assumptions about extra whitespace. But they don't handle the issue well when there's a whitespace in between names.
To achieve the expected behavior, what is needed is just to use the trim()
method, which is easy to implement but can greatly enhance user experience.
add contact -n Aaron Tan -p 12345678 -a Baker Street 12 -e aaron123@gmail.com
andadd contact -n Aaron Tan -p 12345678 -a Baker Street 12 -e aaron123@gmail.com
(there is an extra white space between Aaron and Tan)These two commands should be considered the same based the usage in real life. Because we are obviously referring to the same person. However, the application doesn't detect such duplicate errors.