I have added support for phone numbers like +91 99999 99999 +1 123 123 123 +41 (555) 555 555 9999999999 , etc Regex is: ^((?:.|\n)*?)((tel:)?([+0-9]{2,4}?\s?[0-9\s()]{8,15}))

I have also added a way for user to provide a custom regex, in the linkify method using phoneRegex - which is an optional named parameter, so no breaking change is introduced

Hello!

Great plugin! Saved me so much time fiddling with text spans!!!!

I ran into one problem, I'm pulling text from a database connection and the text is returned with carriage returns and linefeeds, which seems to make the REGEX parser fail. To fix it, I do a text replace of all '\r\n' to simply '\n' and Linkify works perfectly.

Might be something to look at in a future release, but in the interim the fix is easy as in the below code:

Linkify(
  text: widget.kennel['kennelDescription'].toString().replaceAll('\r\n', '\n'),
  style: bodyStyle,
  linkStyle: bodyStyleYellow,
  humanize: true,
  onOpen: (LinkableElement link) async {
    if (await canLaunch(link.url)) {
      await launch(link.url);
    } else {
      Utilities.showAlert(context, 'Unable to open link', 'The app was unable to open ${link.url}', 'OK');
    }
  },
),

Currently, the only way to know if an email address is valid is to send an email address (and potentially wait for an action, like clicking a link to validate, etc.)

tl;dr

Please use this RegExp:

r'.+@.+'

(No need for mailto: too)

Boring stuff below

Some examples for perfectly valid email addresses:

[email protected]
[email protected]
[email protected]
#[email protected]
[email protected]
%[email protected]
&[email protected]
'[email protected]
*[email protected]
[email protected]
[email protected]
/[email protected]
[email protected]
[email protected]
^[email protected]
[email protected]
`[email protected]
{[email protected]
|[email protected]
}[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
someuser@ai.
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
"very.(),:;<>[]\".VERY.\"very@\\ \"very\".unusual"@strange.example.com
[email protected]
admin@mailserver1
#!$%&'*+-/=?^_`{}|[email protected]
"()<>[]:,;@\\\"!#$%&'-/=?^_`{}| ~.a"@example.org
[email protected]
user@localserver
user@[2001:DB8::1]

These addresses above are all valid!

If you really, really want to be kinda (covers 99.99% of the cases) compatible with some of the RFCs, you can use this RegExp (I use it in production, but lately considering to drop it):

r'^([^\x00-\x20\x22\x28\x29\x2c\x2e\x3a-\x3c\x3e\x40\x5b-\x5d\x7f-\xff]+|\x22([^\x0d\x22\x5c\x80-\xff]|\x5c[\x00-\x7f])*\x22)(\x2e([^\x00-\x20\x22\x28\x29\x2c\x2e\x3a-\x3c\x3e\x40\x5b-\x5d\x7f-\xff]+|\x22([^\x0d\x22\x5c\x80-\xff]|\x5c[\x00-\x7f])*\x22))*\x40([^\x00-\x20\x22\x28\x29\x2c\x2e\x3a-\x3c\x3e\x40\x5b-\x5d\x7f-\xff]+|\x5b([^\x0d\x5b-\x5d\x80-\xff]|\x5c[\x00-\x7f])*\x5d)(\x2e([^\x00-\x20\x22\x28\x29\x2c\x2e\x3a-\x3c\x3e\x40\x5b-\x5d\x7f-\xff]+|\x5b([^\x0d\x5b-\x5d\x80-\xff]|\x5c[\x00-\x7f])*\x5d))*\.?$'

More info:

• https://regex101.com/r/flaB8B/1
• https://emailregex.com/email-validation-summary/index.html
• https://haacked.com/archive/2007/08/21/i-knew-how-to-validate-an-email-address-until-i.aspx/
• https://fastapi.metacpan.org/source/RJBS/Email-Valid-0.179/lib/Email/Valid.pm - lookout for the big-ass regex 🙃
• http://ai. oh, would you look at this strange domain 😛

example : facebook.com www.google.com

used loose, http://facebook.com considered url.

if i used loose, all dots (.) consider that url. example. http://1. or something. also considered url.

Please fix it asap.

I am trying two display two URLs with the below code but it's detecting only the first one. This is how it's displaying in the application.

Linkify(
          onOpen: (link) async => {
            if (await canLaunch(link.url))
              {
                await launch(link.url),
              }
            else
              {
                throw 'Could not launch $link',
              }
          },
          text: message,
          style: TextStyle(
            color: color,
            fontSize: fontSize,
            fontWeight: fontWeight,
            fontFamily: Fonts.TITLE,
          ),
          options: LinkifyOptions(humanize: false),
        ),

flutter_linkify: ^3.1.3

[✓] Flutter (Channel stable, v1.17.0, on Mac OS X 10.14.5 18F132, locale en-IN)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2) [✓] Xcode - develop for iOS and macOS (Xcode 11.3.1) [✓] Android Studio (version 3.6) [✓] VS Code (version 1.45.1) [✓] Connected device (1 available)

This commit expands the UrlLinkifier to pick up http://, https://, and www. urls. If the url it picks up doesn't start with http:// or https://, then it will prepend http:// (or https:// depending on linkify options) to make it launchable from urlLauncher.

This PR fixes #40 where a text with both loose and not loose URLs was not being properly parsed.

I've added 2 tests that reproduce the issue and then fixed it.

The main issue is that even if the looseUrl option is set to true, the first match is using the full _urlRegex, so if the text contains both a loose and a not loose URL the first part of the text is parsed as TextElement even it has a loose URL.

I have tried to without https://, Could not able to get the valid url.

Example. I try to give www.facebook.com , facebook.com it's not recognised the valid url. i given the looseUrl option true. All dots (.) considered the url format.

SelectableLinkify( onOpen: onOpen, text: "github.com test.", style: TextStyle(color: Colors.black), linkStyle: TextStyle( color: Colors.blue ), options: LinkifyOptions( looseUrl: true ), ), The above code results in the following text to be highlighted:

The looseUrl option has done a good job of identifying most loose urls but its also highlighting anything with a period at the end. Is it possible to modify the _looseUrlRegex to require there be at least one non-whitespace character?

Hey!

Really thanks for making this package and it has proven to be quite useful for us. There's one issue however that I found. If looseUrl is set to true then words at the end of sentences are also considered as valid links. It disregards the space after the period. I'm not sure if this is the right package for this issue but I'm still going to add it here.

Here's a live example.

And here's a code snippet.

Linkify(
            text: text,
            maxLines: maxLines,
            overflow: TextOverflow.clip,
            textAlign: TextAlign.start,
            options: LinkifyOptions(
              looseUrl: true,
            ),
            onOpen: (link) async {
              if (await canLaunch(link.url)) {
                await launch(link.url);
              }
            },
)

I'm using package version flutter_linkify: 3.1.2 and flutter version 1.12.13+hotfix.8.

Looking forward to hearing from you! Thanks again for this package. Cheers.

A "." at the end of a link should not highlighted. Like: www.google.de.

Code:

Linkify(
    style: _greyTextStyle(context),
    linkStyle: linkStyle(context),
    text: "Besuche für weitere Informationen einfach https://www.sharezone.info.",
)

Result:

The text argument is not passed here. It results in loosing original text (httpor httpsis added)

https://github.com/Cretezy/linkify/blob/e5e1b7ef5ba28e94841744eb62ee72f6bcb3e44b/lib/src/url.dart#L72

For example, in the link (example.com/over/there?name="ferret") it is highlighted until the quotation mark. Edit: Only applicable for loose URL.

The regex used on UserTagLinkifier contains a negative lookbehind, which is unsupported on Safari.

In order to being able to use the linkifier on Safari, I removed the lookbehind from the regex and refactored the code to do the same thing that the original regex.

I also fixed some user tag tests that were failing.

Current State

Currently there is not a way to capture the original text that contributed to a LinkifyElement. Instead, only the modified text is available.

Desired State

A LinkifyElement has the property originText where the original text is captured.

Why

An example of this is when parsing text containing a URL i.e.

ssuper.co is one way to specify a website, https://ssuper.co is another way

If using humanize=False, we get this when we recreate the phrase from the parsed elements

https://ssuper.co is one way to specify a website, https://ssuper.co is another way

Or, if using humanize=True, we get this

ssuper.co is one way to specify a website, ssuper.co is another way

This is an issue when using Linkify to parse text for a TextEditingController. Because the original text is not recoverable from LinkifyElement, there is no way to reliably mirror the original text the user types. Having an originText property fixes this.

Current Workaround: https://stackoverflow.com/a/65914757