Open xGladiate opened 1 week ago
Severity: Low
Response: NotInScope
Even though this was not included in the error message email format, according to common email specifications, the local part of an email cannot contain consecutive dots unless quoted, which is a very rare occurrence. Hence, in our opinion, Low severity would be more appropriate.
We believe this is out of scope of the current iteration as the value provided by supporting it will be minimal (as this is a very rare edge case and our product's primary focus is public address management) and the command fails gracefully when they try to do so.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
Issue
The email
John..Doee@example.com
could not be added into the system although the email is valid based on the constraints give.Steps to reproduce:
add n/John Doee p/98765432 e/John..Doee@example.com a/311, Clementi Ave 2, #02-25 t/friends t/owesMoney
Although the email is valid, based on the error message - which indicates that the use of.
is allowed. The contact with this email could not be added into the system. As after inputting this line, an error message would be shown.Suggestion
Allow the addition of such input into the system.