I'm aware that this issue has already been fixed in 9038dd7, but it has not been released yet.

Please release 2.0.3 so that the fix can be used, would also be nice if flutter_linkify can update to [email protected] straight after.

Thanks for the great work!

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');
    }
  },
),

I would request to detect mobile and telephone numbers and make them clickable, same as react-native.

It seems there is no link highlighting if there is a \r in the text section. Can it be fixed? Thanks in advance !

Hi! How difficult would it be to add support for phone numbers? I am willing to contribute on this issue if guidance is provided.

Hi,
Is it possible to highlight hashtag?
Thanks!

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

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.

Issue:

Currently, the following patterns of text are being identified as url when looseUrl option is true when using linkify.

pattern1 -> 'awdaw....aw'
pattern2 -> 'awdaw...wad...wadw'
and so on...

Expected behaviour:

Technically, this shouldn't be identified as urls as there are multiple periods present consecutively and thus is an invalid url pattern.

Bare domains like google.com without www or http headers are not parsed.

When a \r escape character is in the string given to the Linkify widget, anything after that escape character does not become a clickable hyperlink. This is a problem as I'm getting information from an API but the data returned contains \r\n for newlines (which is a common escape character sequence). A workaround is to simply remove all \r escape characters from the string but there wasn't any indication that was needed.

Example:
Note: onOpen code has been omitted for simplicity.
No \r
Linkify( text: 'https://www.google.com\nhttps://www.google.com', )
This code works fine as it does not contain \r.
Has \r
Linkify( text: 'https://www.google.com\r\nhttps://www.google.com', )
This code will cause only the first URL to become hyperlinked. The second one will not become hyperlinked as it is after the \r escape character. Using looseURL does not resolve the issue.

This may be the same issue as Cretezy/flutter_linkify#47 but I cannot say for sure as the source string is not provided.

Something like this in text:

Would you like to visit [Google](https://www.google.com)?

Will be rendered as

Would you like to visit Google? (in blue, of course)

You can use flutter_markdown package for this?

Congratulations for your excellent package!

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 😛

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.

The part of the loose url regex recognizing the domain is [a-z]{2,4} (https://github.com/Cretezy/linkify/blob/master/lib/src/url.dart#L10) while nowadays there are many domains name with more than 4 letters like .design, .travel, .cloud, etc.

Any link with a comma at the end, i.e. ("https://github.com,") will contain the comma in the link. Thus, when the link is launched, the web page will fail to load because the url is not valid.

First, thanks for this nice package.
Currently when link is placed inside parentheses, ex: "Some text before (https://github.com/Cretezy/flutter_linkify).", this URL is parsed together with closing parentheses ")" making it invalid URL. Result: https://github.com/Cretezy/flutter_linkify)
Would it be possible to exclude parentheses/brackets when they are wrapped around the URL string?

It would be nice if this library and flutter_linkify recognized custom schemas for deeplinks.

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:

www.yahoo.com isn't found as a link, only http://www.yahoo.com. Anything that has www before it should be considered a link, IMO.

When you have a text like example.com and http://example.com and use the looseUrl: true LinkifyOption, the first URL is not being parsed as an UrlElement, but if you have the text example.com and example.com it works as expected.

I've run this test:

expectListEqual(
    linkify(
        'example.com and http://example.com', 
        options: LinkifyOptions(looseUrl: true),
    ),
    [UrlElement('http://example.com', 'example.com'),
    TextElement(' and '),
    UrlElement('http://example.com', 'example.com')]
);

And gives this output:

Expected: <true>
Actual: <false>
Expected 
    [TextElement: 'example.com and ', 
    LinkElement: 'http://example.com' (example.com)] 
to be 
    [LinkElement: 'http://example.com' (example.com), 
    TextElement: ' and ', 
    LinkElement: 'http://example.com' (example.com)]

While this test runs ok

expectListEqual(
    linkify(
        'example.com and example.com', 
        options: LinkifyOptions(looseUrl: true),
    ),
    [UrlElement('http://example.com', 'example.com'),
    TextElement(' and '),
    UrlElement('http://example.com', 'example.com')]
);

Hello, the UserTagLinkifier does not support languages like Russian, Litvanian and others which is not Latin Alphabets.

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.

The text ...and is parsed as an URL while the text ..and is not.

Test to reproduce it:

expectListEqual(
    linkify("...and", options: LinkifyOptions(looseUrl: true)),
    [TextElement('...and')],
);

Output:
Expected [LinkElement: 'http://...and' (...and)] to be [TextElement: '...and']

This test runs ok:

expectListEqual(
    linkify("..and", options: LinkifyOptions(looseUrl: true)),
    [TextElement('..and')],
);

When I turn on loose url detection it will create a link at the end of any sentence containing a "."

can you provider a UserTagLinkifier sample?

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?

It looks like email is not recognized for the following string: "[email protected] and http://google.com"

In my chat app, the www looks like extra information no one cares about - and also looks very ugly.

For this link https://www.youtube.com/watch?v=q6MF3OIhW8I humanize removes the https:// part.

Can you please
A make humanize remove www
or
B. add a new option to remove www
or
C. make humanize an enum {RemoveHTTP, RemoveWWW}
?

The visual result would be youtube.com/watch?v=q6MF3OIhW8I

Thank you for your great work!

Going to move to parsing library and will address shortly

Originally posted by @Cretezy in #22 (comment)

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)

The text argument is not passed here. It results in loosing original text (http or https is added)

Add support for phone numbers so they could be opened easily