Invalid emails are still accepted in add

[dohaduong]

Using the command add n/John Day p/98765432 e/just@example a/John street, block 123,#01-01 m/computer science, the email is clearly invalid - just@example, where the domain is invalid, the app still accepts this as a valid email.

The DG appendix for planned enhancement has not mentioned this bug also, thus, I would say this is a feature flaw which could be improved in the future version as users should be prompted of the invalid email address similar to this.

[soc-pe-bot]

Team's Response

Both are concerned about the validity of invalid domains as an email input.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Invalid email with invalid domain are accepted

Using command add n/K e/[email protected], the app still accepts the email as an invalid email, even tho the domain is clearly invalid.

Thus, as the DG/UG did not mention anything regarding this, I will consider this as a feature flaw

---

_{[original: nus-cs2103-AY2223S2/pe-interim#1077] [original labels: severity.Low type.FeatureFlaw]}

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

We accept this as a feature flaw however we believe that this is not in scope for these reasons:

• Emails are hardly the main aspect of TeamBuilder.
• Most users are unlikely to use IP address in their emails.
• This is a foreseeable future enhancement
• When users tries to send an email to an invalid email address, they will know right away.

Emails are also difficult to check for due to the many possible variations. Below is an excerpt of valid email addresses according to wikipedia:

We believe that this is more of a 'nice to have feature' than a feature flaw

Items for the Tester to Verify

❓ Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

• I disagree

Reason for disagreement: I disagree that these 2 bug reports are duplicates, this is because one of them has invalid domain as a combination of number ("111.222..."), whereas the other one only contains letters ("@example").

I have specifically separated these 2 bug reports as the input and the error itself is different.

---

❓ Issue response

Team chose [response.NotInScope]

• I disagree

Reason for disagreement: The team did not mention in both UG and DG that they will be improving/fixing/taking into account the complexity of valid email domain/email and thus, I would still consider this a valid feature flaw.

---