Open nigellqx opened 1 week ago
There is a workaround of using the original NUS email, E1234567@u.nus.edu for instance.
[The team marked this bug as a duplicate of the following bug]
Valid email not accepted
Based on the UG and error message,
A123++A@example.com
is an allowed email address as the local part is alphanumeric + allowed special char, and does not start or end with special char. However, it is not allowed in the app. While the planned enchancement says that it is planned to "increase the flexibility of email validation", I belive this is different since it is a mismatch of behaviour between the UG and the application. Hence it is a functionalityBug and not a feature flaw covered by planned enchancement.
[original: nus-cs2103-AY2425S1/pe-interim#2701] [original labels: severity.Low type.FunctionalityBug]
[This is the team's response to the above 'original' bug]
Similar to #1847.
There is a workaround of using the original NUS email, E1234567@u.nus.edu for instance.
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
Reason for disagreement: [replace this with your explanation]
When the email has 2 "_", it does not let me add the contact. This is not specified in the field restrains where they cannot be 2 consecutive special characters.