[Conformance] Expand valid email tests to cover semi-valid email address values #136
Labels
Conformance
Related to the conformance testing cases or harness
Feature
New feature or request
Good First Issue
Good issues for first-time contributors
If implementations of the
isEmail
custom CEL expression use an address parsing library, the input might contain extraneous whitespace that the parser automatically cleans (e.g.," [email protected] ".isEmail()
might evaluate to true). This goes against the spirit of thefield.string.email
constraint. We should add similar conformance tests that cover these cases (a'la the fix for this bug in protovalidate-go).The text was updated successfully, but these errors were encountered: