Open yleeyilin opened 2 months ago
It is indeed a valid issue to take note of within the application. Though the application should still allow such input instead of making the validation too restrictive per se. Thus, we decided that the best approach to resolve such issue is to implement a warning message to the user in the upcoming releases specifying that there are extra empty spaces detected in the name. Thus, it can be considered as NotInScope
.
Team chose [response.NotInScope
]
Reason for disagreement: I agree with your groups conclusion that the best approach is "to implement a warning message to the user in the upcoming releases specifying that there are extra empty spaces detected in the name" but I do not quite understand why it would be considered NotInScope
given that your group conceded that such input should be handled.
Steps to reproduce:
edit 18 n/John
Doe
, which has extra spacing between John and Doe.Expected:
Actual:
Screenshots:
This is problematic as it is not suited for fast typists who may make accidental spacing errors when keeping it. You can consider supporting this for better convenience and usability for your users. One way you can do is by parsing the name and reformatting it for the users.