Open ezeAng opened 1 year ago
This does not affect the functionality as user may wish to input multiple whitespaces on purpose. Restricting this will not provide any value to the users.
Team chose [response.NotInScope
]
Reason for disagreement: A user is very likely to input an additional white space without knowing and is almost never going to input extra white spaces for the sake of differentiation between events, I do not think this is an intended behaviour. This will cause inconveniences and confusion when there are overlapping events with the same name but separate details. There should be a restriction or warning that prevents such confusion.
I would think it is a low severity bug, as users can still manually edit the names and clear confusion.
Event "fish at wedding" is seen as a different event to "fish at wedding", could be a common typo error when dealing with more events. User could have accidentally added multiple events and not noticed the slight difference of an additional whitespace, and possible double book 2 different contact lists.
However, assuming the user is careful, this should not happen.