You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, the reader is not informed that phone numbers must be at least 3 digits long and emails must have a name and a domain. The examples, though helpful for regular operations, does not illustrate all these constraints fully
We appreciate your valid concern about the constraints. The preventive measures in disallowing users of our application to add a person with a 1-2 digit phone number or an email without domain are primarily meant to act as a safety net for typographical errors. We believe that it is a rare case that a user actually intends to input a phone number with 1-2 digit(s) or input an email without domains, as it is extremely rare to have such phone number or email.
Moreover, we did not impose any further constraints on what a phone number or email could be such that additional clarifications are needed. Such constraints could often include restrictions to email domains or restrictions to the number of digits in a phone number specific to any country. While specifically stating the constraints does no harm, our team took the approach to concisely and sufficiently guide readers with the use of concrete examples to improve their understanding of what a phone number and email constitute.
These restrictions are also spelled out very clearly in error messages.
For example, the reader is not informed that phone numbers must be at least 3 digits long and emails must have a name and a domain. The examples, though helpful for regular operations, does not illustrate all these constraints fully
[original: nus-cs2103-AY2122S2/pe-interim#3540] [original labels: severity.Low type.DocumentationBug]
The text was updated successfully, but these errors were encountered: