Open wxiaoyun opened 3 months ago
This works as intended, because emails cannot have consecutive periods in the real world. Suppose this is a typo by the user, rejecting it is expected.
It would be too tedious to include all possible edge cases of email validation for the local part (consecutive periods, registered domain name etc..). Thus, we put this as NotInScope, since to include all possible edge cases in the UG has a lower priority than the work already done in v1.4, the email validation works as intended, and for the benefit of the user.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
Description
Steps to reproduce
add /com Google /desc test /status to_apply /poc Test Name2 /email test..valid@email.com /phone 99999999
Expected
Actual
Potential Suggestions
Screenshots