-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
String not recognized #41
Comments
if you add a protocol prefix it should work just fine: |
Thanks, but I don't control the strings to be linkified - I get them from user input. |
@infojunkie, the domains without a scheme are detected using node-tlds.
|
Sorry but I don't think I understand your explanation:
|
Ok, I got it. |
@infojunkie - As mentioned above, you should see if this can be resolved through linkify-it. Additionally, you'll have the flexibility to support this on your own in const matchDecorator = (text) => {
// Implement your matching logic here to support iTunes:bit.ly/oaKTSQ
};
<Linkify matchDecorator={matchDecorator}>
...
</Linkify>
Any feedback is appreciated. |
The following string
iTunes:bit.ly/oaKTSQ
does not get linkified whereasiTunes: bit.ly/oaKTSQ
does. It's a bit ambiguous of course, but do you suggest any option to support it?The text was updated successfully, but these errors were encountered: