Open lim-jt opened 5 days ago
Thanks for the suggestion! However, considering alternative forms of input for phone numbers is not in scope due to the following reasons: (1) It does not make the app more significantly and reasonably useful as typing phone numbers without space is a valid and widely used format. (2) Optimisation for fast typing (typing a hyphen or space within numbers may hinder typing and cause error inputs).
Team chose [response.NotInScope
]
Reason for disagreement: I disagree that this is not in scope as this example is used in the guidelines for triaging PE bugs in the CS2103T website!
While specified by the UG that phone numbers can only contain numeric numbers with no space, this is an unnecessarily overzealous input validation as it is still correct and natural for some users to input numbers with a space e.g. 8123 4567 or 8123-4567