URL parsing errors

[szuperaz]

The following URL formats are not parsed correctly:

• google.com -> not clickable
• www.google.com -> clickable, but navigates to the wrong URL

[TobiasHesselinkTopicus]

Some additional information:

• google.com and www.google.com
  Channel message html property does not include an <a href..../> element while there is a URL.
  For example: <p> Some text message with a URL inside it, like google.com </p>
• https://google.com
  Channel message html property does include an <a href..../> element while there is a URL.
  For example: <p> Some text message with a URL inside it, like <a href="https://google.com"/> </p>

[TobiasHesselinkTopicus]

@szuperaz is there any update on this? It's been a while and no fix has been released. It would be very helpful for us to use URL enrichment, but because all URL's has to be prefixed with http(s), this functionality is not usable for now unfortunately.

A fix for this would be very much appreciated.

Thanks in advance.

[github-actions]

🎉 This issue has been resolved in version 5.11.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀