Advanced email parsing added; eg: Full Name email@domain.com #276
Conversation
This file contains 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
|
@maranqz this is for you! 🙂 It's not done yet since it turned out to be a massive change. I still want to do more testing of my own, but it would be awesome if you could test it out for me too and let me know if it works for you too! |
Codecov Report
@@ Coverage Diff @@
## master #276 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 83 83
Lines 9756 9846 +90
Branches 1562 1603 +41
=========================================
+ Hits 9756 9846 +90
Continue to review full report at Codecov.
|
caronc
force-pushed
the
271-advanced-email-parsing
branch
from
99ac376 to
353864b
Compare
|
@caronc |
caronc
force-pushed
the
271-advanced-email-parsing
branch
from
633495e to
40badd1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description:
Related issue (if applicable): #271
Email addresses can now be parsed as:
Full Name user@domain.comFull Name: user@domain.comFull Name <user@domain.com>Full Name : <user@domain.com><user@domain.com>As well as the legacy format:
user@domain.comlabel+user@domain.comSome providers (such as SMTP/EMail will use the
Full Nameand incorporate it in the email. For example:mailto://user:pass@gmail.com/Joe%20Rogan:jr@joerogan.netwould log into yourgmailaccount and associate Joe Rogan with the To emailjr@joerogan.netmailto://user:pass@gmail.com/?cc=Uncle%Ben:ben@unclebens.comwould log into yourgmailaccount and send an email to you while CCingben@unclebens.comand associating Uncle Ben with it.bccandccwhich in itself also supports the new email messaging formatChecklist
flake8)