Email validation constraint too loose

[TehOPanas]

After trying out the product, I discovered that the constraint for the email field is a bit loose given that emails like a@bc are allowed to be entered even though this is clearly not a valid email.

I suggest the development team can maybe reference some standards from RFC or OWASP

[nus-se-script]

Team's Response

We agree that this is a valid concern. However, when our team was discussing restrictions for email, we wanted to implement a restriction that was flexible enough to prevent overzealous input validation.

Validation of every possible email is also not a trivial task and hence it is not as important as the current features as explained in nus-cs2103-AY2324S1/forum#336. Hence, we have categorised this bug report as NotInScope.

Items for the Tester to Verify

❓ Issue response

Team chose [response.NotInScope]

• I disagree

Reason for disagreement: [replace this with your explanation]

---