Domains get extracted from copied emails
See original GitHub issueShort description
When copying an email or a text containing an email, the paste-shortcuts suggest both the email itself, as well as the email-provider’s domain.
Steps to reproduce
Copy this text:
example@email.com
or this text
Lorem ipsum example@email.com asdf jklgg.
Environment information
- FlorisBoard Version: 0.4.0-alpha01 (87)
- Install Source: Google PlayStore
- Device: Samsung Galaxy S9
- Android: 10
Issue Analytics
- State:
- Created a year ago
- Comments:21 (11 by maintainers)
Top Results From Across the Web
19 Best Email Extractors: Collect Valid Emails Instantly (Sales)
They can extract emails from website domains, social networking sites, and segments of copy text. These tools automate the process to save ...
Read more >How do we extract email addresses using the domain? - Quora
1- go to the website you want to extract the email from · 2- right click ——-> show source code of the page...
Read more >Email Extractor - Domain Check
Extract emails, email addresses, and email domain names from any text, links, URLs, HTML, CSV, XML, email list, or list of your contacts....
Read more >Extract unique domain names from list of email addresses
00:00 Extract the unique domains from a list of email addresses00:10 Separate the email address to show the domain name only00:45 Remove the ......
Read more >How to extract domain from e-mail addresses in Google Sheets.
How to extract domain from e-mail addresses in Google Sheets. ... Simply copy the formula below and paste it into cell B2.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think for now I will let the .{url} as {url} categorization as is. Should it really pose a problem in the future it is a straightforward fix by adding
(?<!\.)
before the host expression.I will now merge in the changes and release them in some days in 0.4.0-alpha02. Thanks everyone for the feedback!
I actually use the negative ones of that group family to prevent long numbers getting detected as 2 separate ones. I have thought of using a positive look-ahead but can’t wrap my head around how the look-ahead can look “over” the phone number to see if there is a parentheses after the number.
Because that’s how Android also seem to handle a dot before a domain, so I inherited this behavior. I could add a negative look-behind, but I am not sure on that one.
Issue is attached to linked PR, so once I merge the branch in this will auto-close 😃