Double closing curly braces ( }} ) seem to break the detection

[eramdam]

Consider this string

Here is a link https://domain.com/d/foo?email={{foo.bar}}&name={{foo.name}}

Even though curly braces are not common in URL, one would expect for https://domain.com/d/foo?email={{foo.bar}}&name={{foo.name}} to be matched to an actual link.

However linkify-it seems to stop matching after the 2nd } character in the URL, resulting in these matches:

[ Match {
    schema: 'https:',
    index: 3,
    lastIndex: 44,
    raw: 'https://domain.com/d/foo?email={{foo.bar}',
    text: 'https://domain.com/d/foo?email={{foo.bar}',
    url: 'https://domain.com/d/foo?email={{foo.bar}' },
  Match {
    schema: '',
    index: 53,
    lastIndex: 61,
    raw: 'foo.name',
    text: 'foo.name',
    url: 'http://foo.name' } ]

Notice how foo.name is being matched as another link because of that 😅

Once again, I know that { and } are not valid characters per the RFC, but Slack and other softwares correctly match this case so I guess there's something that can be done to fix that in linkify-it 😊

I'm happy to provide more details/examples.

[puzrin]

Looks like dupe of #23. IMHO worth to RIP one more example there :)

[puzrin]

I thinks this does not needs fix in linkify-it, but you can add kludge to your app: replace {{ and }} with something unique and non-breaking-link, and replace back after linkify run. That's dirty, but may be ok for your specific case.

[githubflub]

This is still an issue. >:[

[puzrin]

@eramdam hi after many years :). I'd like to clarify status of this issue.

• is it critical or can be rejected?
• should we consider it as part of Better handle nested parens #23 or as special case?

[puzrin]

Close as dupe of #23