Open KhoonSun47 opened 4 months ago
Hello, thank you for sharing your observation regarding email validation!
However, we'd like to point out that the case you've mentioned, where an invalid email address like "abc@12.34" is accepted, typically occurs when there's a user error during data entry ie HR manager type wrongly. These instances are very rare, as they require incorrect input that deviates significantly from common patterns of email addresses. Given that the majority of users are HR managers who are familiar with standard email address formats, this scenario should not be common in everyday use.
While we acknowledge that the system's validation could be stricter to align with IETF standards, we believe the impact of this issue is limited to extreme cases. Nonetheless, we will consider your feedback as future enhancements to HR Connect.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
Steps to reproduce:
Actual Output: Step 1: Entering an invalid email address "abc@12.34" to this person "John LOL"![image.png](https://raw.githubusercontent.com/KhoonSun47/pe/main/files/c0c64497-5d40-4bbc-9d73-77cc6d135046.png)
Expected Output: This should be rejected as it is an invalid email address.
Suggestion: I believe that the validation for the email address could be stricter, to follow the format for the IETF standards.