Remove exactly one closing angle bracket after a display name - #176
Merged
Merged
Conversation
rstrip('>') removed any number of them, so 'Me <[email protected]>>' was
accepted.
Owner
|
TY |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
With
allow_display_name=True,Me <[email protected]>>validates as[email protected].split_emailremoves the closing bracket with.rstrip(">"), which strips any number of them, whileMe <[email protected]> >is already rejected. The check just above makes sure the part ends with>, so this slices off exactly one.Inputs with an extra
>now fail with the existing "invalid characters: '>'" error. In a sweep comparing before and after over 1,192 inputs, only those ending in>>changed.Written with AI assistance (Claude); I have reviewed the change.